Radar #20

Nov 2–8, 2026 · Published Nov 2, 2026, 8:34 PM UTC

Fleet snapshot

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

489 repositories were scanned for AI-context hygiene.

1772 AI-context risk signals matched 20 sensitive path categories.

1% of scanned repos use a dedicated AI exclude file (2 types 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

489
repos in this week's stats

AI-context risk signals

1772
sensitive path matches

Repos with risk signals

26%
125 of 489 repos

AI exclude-file coverage

1%
repos with a dedicated AI exclude file
Scan details
Targeted
500
Scanned
489
Scan complete
489
Skipped
0
Errors
11
Repos with risk signals
125
Generated
Nov 2, 2026, 8:34 PM UTC
Tool version
0.21.0–0.21.0
Ruleset
e634955c141dcfc6

Main takeaway

26% of scanned repos had AI-context risk signals — mostly lower-severity path categories.

Far fewer repos use a dedicated AI exclude file (1%) than show risk signals (26%). Start by excluding Environment files (.env) and Log Files from AI context.

AI-context risk signal categories

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

  • Environment files (.env)Required41 repos · 122 matches
  • Key material (.pem, .key)Required29 repos · 106 matches
  • Key FilesRequired6 repos · 16 matches
  • Credentials JsonRequired1 repo · 6 matches
  • Secrets YamlRequired3 repos · 3 matches
  • npm credentials (.npmrc)Recommended21 repos · 31 matches
  • Android KeystoreRecommended13 repos · 13 matches
  • Terraform VarsRecommended2 repos · 11 matches
  • Firebase Client ConfigRecommended6 repos · 10 matches
  • Yarn ConfigRecommended8 repos · 10 matches
  • Pkcs12 PfxRecommended3 repos · 4 matches
  • Auth JsonRecommended1 repo · 3 matches
  • Android Local PropertiesRecommended1 repo · 1 match
  • Pgp KeysRecommended1 repo · 1 match
  • Pkcs12 P12Recommended1 repo · 1 match
  • Vpn Rdp ConfigsRecommended1 repo · 1 match
  • Log FilesInfo29 repos · 1281 matches
  • Data ExportsInfo5 repos · 135 matches
  • Backup FilesInfo4 repos · 16 matches
  • Local DatabasesInfo1 repo · 1 match

AI exclude files

1% of repos use a dedicated AI exclude file

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

.cursorignore
0%
.claudeignore
0%
.aiexclude
0%
.geminiignore
0%
.copilotignore
0%
.llmignore
0%
Show 9 more exclude file types (2 in use overall)
.aiderignore
0%
Claude Project Rules
0%
.clineignore
0%
.codeiumignore
0%
.codyignore
0%
.continueignore
0%
.cursorindexingignore
0%
.rooignore
0%
.zedignore
0%

AI context files

29% 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.

AGENTS.md
24%
CLAUDE.md
17%
Cursor project rules
0%

Fix the top risks

Patterns covering this week's most widespread categories (Environment files (.env), Certificates and PEM keys (.pem), npm credentials (.npmrc), Android keystores (.jks, .keystore)). 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
*.pem
*.key
certs/
.npmrc
*.jks
*.keystore
keystore.properties

Per-category guidance lives in the risk pattern guides.

Compared with previous report

MetricRadar #19Radar #20
Repositories scanned490489
AI exclude-file coverage0%1%
Repos with risk signals31%26%
AI-context risk signals (absolute)8371772
Risk signals per scanned repo1.73.6
Top categoryLog FilesLog Files

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

125 of 489 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.

Scan with Offsend CheckLearn more about Offsend →