Fleet snapshot

Anonymous counts across all complete scans this week. No repository names are shown.

496 repositories were scanned for AI-context hygiene.

3668 AI-context risk signals matched 28 sensitive path categories.

0% of scanned repos use a dedicated AI exclude file (1 type in use).

How to read this report

These are not confirmed leaks.

Radar uses path-level checks to detect files and folders that may become visible to AI coding tools if they are not covered by AI-specific ignore rules.

A risk signal is a file committed to the repository whose path matches a sensitive category (for example .env or *.pem). Counts are file matches at the path level — Radar never opens the files.

  • No file contents were read.
  • No secrets were collected.
  • No repository names are published without opt-in.
  • Repositories are a manually curated cohort, not a random sample — read these as directional signals, not population-level statistics.

Scanned

496
repos in this week's stats

AI-context risk signals

3668
sensitive path matches

Repos with risk signals

29%
145 of 496 repos

AI exclude-file coverage

0%
repos with a dedicated AI exclude file
Scan details
Targeted
500
Scanned
496
Scan complete
496
Skipped
0
Errors
4
Repos with risk signals
145
Generated
Sep 28, 2026, 5:58 PM UTC
Tool version
0.21.0–0.21.0
Ruleset
e634955c141dcfc6

AI-context risk signal categories

Aggregated path pattern counts — not tied to any named repository.

  • Key FilesRequired19 repos · 522 matches
  • Key material (.pem, .key)Required16 repos · 173 matches
  • Environment files (.env)Required38 repos · 83 matches
  • Secrets YamlRequired5 repos · 5 matches
  • Keepass DatabasesRequired1 repo · 2 matches
  • Credentials JsonRequired1 repo · 1 match
  • Secrets JsonRequired1 repo · 1 match
  • Docker configRecommended2 repos · 1814 matches
  • npm credentials (.npmrc)Recommended38 repos · 45 matches
  • Firebase Client ConfigRecommended11 repos · 23 matches
  • Android KeystoreRecommended10 repos · 15 matches
  • Yarn ConfigRecommended7 repos · 14 matches
  • Pkcs12 P12Recommended5 repos · 7 matches
  • Pkcs12 PfxRecommended4 repos · 6 matches
  • Apple P8 KeysRecommended2 repos · 3 matches
  • Auth JsonRecommended2 repos · 3 matches
  • Terraform VarsRecommended1 repo · 2 matches
  • Vpn Rdp ConfigsRecommended1 repo · 2 matches
  • Agent TranscriptsRecommended1 repo · 1 match
  • Android Local PropertiesRecommended1 repo · 1 match
  • Htpasswd FilesRecommended1 repo · 1 match
  • Pgp KeysRecommended1 repo · 1 match
  • Spring Local ConfigRecommended1 repo · 1 match
  • Log FilesInfo35 repos · 895 matches
  • Backup FilesInfo12 repos · 32 matches
  • Data ExportsInfo2 repos · 7 matches
  • Db DumpsInfo1 repo · 4 matches
  • Local DatabasesInfo2 repos · 4 matches

AI exclude files

0% of repos use a dedicated AI exclude file

These actually keep matching files out of AI context — and they are still rare.

Show 9 more exclude file types (1 in use overall)

AI context files

28% of repos ship an AI context file

Files like AGENTS.md and CLAUDE.md give AI tools project instructions — theyadd context, they do not exclude anything. They are not a substitute for an exclude file.

Fix the top risks

Patterns covering this week's most widespread categories (Environment files (.env), npm credentials (.npmrc), Private keys (.key), Certificates and PEM keys (.pem)). Add them to a dedicated AI exclude file (for example .cursorignore or.claudeignore) — and to .gitignore so the files are never committed.

AI exclude rules
.env
.env.*
!.env.example
.npmrc
*.key
*.pem
secrets/
certs/

Per-category guidance lives in the risk pattern guides.

Compared with previous report

MetricRadar #14Radar #15
Repositories scanned497496
AI exclude-file coverage1%0%
Repos with risk signals31%29%
AI-context risk signals (absolute)34573668
Risk signals per scanned repo7.07.4
Top categoryLog FilesDocker config

Named participants

Per-repository reports for maintainers who opted in. Fleet counts above stay anonymous; each card below is that repo's own scan.

No named listings this week. Maintainers can opt in via radar registry.

View all-time participants →

Check your own project

145 of 496 repos this week exposed sensitive paths to AI tools. Check yours in seconds:

Run the same local check with Offsend CLI:

brew install --cask offsend/tap/offsend-cli
offsend show
offsend prepare --dry-run

Everything runs locally. No file contents are uploaded.