Skip to main content
Snare ships 18 canary types in three tiers. The tier tells you how reliably it fires and whether it has side effects on your own tooling.

Precision (3)

Fire via SDK or OS hooks that already exist. Near-zero false positives. No side effects. These are the default (snare arm plants all three).

High reliability (5)

Fire when the credential is actively used — by anyone. Human attacker, compromised agent, leaked key, automated scanner. Some have side effects on your own tooling; read the notes before enabling.

Medium reliability (10)

Fire conditionally. The attacker must also honor the SDK base URL override. A human who grabs the key and calls the real API directly won’t trigger these.

Planting canaries

Side effects

PyPI adds extra-index-url to your pip config. Every pip install on this machine will query snare.sh as an additional index. Package names appear in request metadata. Run snare teardown --type pypi to remove. npm adds a scoped registry entry. Only packages under the fake scope are affected. Terraform creates ~/.terraformrc with a fake provider namespace. Fails if ~/.terraformrc already exists (to avoid breaking existing HCL config).