Skip to main content
snare arm defaults to precision mode — three canaries that fire via existing SDK and OS plumbing, with near-zero false positive risk.
Use --select to pick canaries interactively, or --all to plant all 18 types.

Why these three

These canaries share a property: they fire via SDK or OS hooks that already exist. No new processes. No DNS dependency. No side effects on your own tooling. Near-zero (not zero) because a randomly-generated profile name could theoretically collide with an existing one, or a tool that iterates all kubeconfigs could trigger k8s. In practice this doesn’t happen.

When to use —select instead

The interactive --select mode lets you pick individual canaries from all three tiers:
Arrow keys to navigate, Space to toggle, Enter to confirm. Precision canaries are pre-checked. Use this when you want aws or gcp coverage in addition to the precision defaults.

When to use —all

--all plants all 18 canary types, including dotenv-based ones (openai, anthropic, huggingface) and types with side effects (pypi, npm). Read the canary types overview before enabling these.

Why not more precision canaries?

Some canaries that look like precision candidates aren’t:
  • azure — service-principal-credentials.json is not in the standard Azure SDK credential chain. Requires an agent to explicitly find and load the file.
  • gcp — sa-*.json is not in ADC auto-discovery. Requires GOOGLE_APPLICATION_CREDENTIALS or explicit file load.
  • git — credential.helper only fires after an HTTP 401 from the fake host. The fake hostname has no DNS record, so git fails at DNS before requesting credentials.
These are high or medium reliability, not precision.