Kingfisher

Secret detection and live validation scanner for Forgejo repositories, using MongoDB’s open-source Kingfisher tool.

Quick Reference

PropertyValue
Namespacekingfisher
Imageregistry.ops.eblu.me/blumeops/kingfisher (see argocd/manifests/kingfisher/kustomization.yaml for current tag)
ScheduleSunday 4am (after Prowler k8s scan at 3am)
Reportssifaka:/volume1/reports/kingfisher/ (NFS)
Manifestsargocd/manifests/kingfisher/
Upstreamforge.eblu.me/mirrors/kingfisher (GitHub mirror)

What it does

Runs as a weekly CronJob that scans all Forgejo repos (eblume + all orgs) for leaked secrets, API keys, and credentials. Produces timestamped HTML reports on the sifaka NFS share. Uses --clone-url-base to route git clones via the internal tailnet instead of the public Fly.io proxy.

Uses the Forgejo/Gitea API to enumerate repos, then clones and scans each one. Validation is enabled (secrets are tested against their respective APIs to confirm they’re live). Reports are HTML only.

Pre-commit hook

Kingfisher also runs as a prek hook alongside TruffleHog for comparative secret detection coverage. The hook uses --staged mode (only checks staged files) with validation disabled for fast, offline-safe commits.

Known false positives

  • Postgres URL with op:// template — 1Password External Secrets template references match the postgres connection string pattern. Not a real credential.
  • GitHub legacy secret key in .git/ — git commit SHAs are 40-char hex strings matching the old GitHub PAT format. Only appears in full-repo scans, not --staged mode.

Ad-hoc scan

kubectl create job --from=cronjob/kingfisher kingfisher-manual -n kingfisher --context=minikube-indri
kubectl logs -f job/kingfisher-manual -n kingfisher --context=minikube-indri

Limitations

  • Built from a sporked fork with a local --clone-url-base patch. See build-spork-container for the build process.
  • Only one output format per invocation. Currently producing HTML only.

See also