Inorganic fork-inflation pattern: 273 forks, 273/273 issues-disabled, burst of 38 on day 5

[tg12]

Summary

unicodeveloper/globalthreatmap was created on 2026-01-22. A full snapshot of all 273 forks shows a pattern inconsistent with organic adoption.

I am not asserting purchased engagement as fact. The evidence supports the narrower claim: the fork pattern is inconsistent with genuine developer interest.

Snapshot findings

• Total forks: 273
• Issues disabled: 273 / 273 (100%)
• Issues enabled: 0
• Zero-star forks: 258 / 273

Burst pattern

Largest fork-creation days — the repo was 2–5 days old during the first spike:

Date	Forks
2026-01-27	38
2026-01-24	31
2026-01-23	26
2026-01-26	23
2026-02-07	13
2026-02-05	11

38 forks on a single day, in the first week of a new repository's life, with every fork showing zero engagement and issues universally disabled, is a strong signal of coordinated or synthetic activity.

Why this matters

If fork counts are inflated by synthetic accounts, readers are misled about:

• downstream adoption
• developer interest
• project legitimacy as an OSINT platform

Recommended next steps

1. Sample accounts from the burst days for profile quality and cross-repo behaviour
2. Do not present fork/star count as a trust signal until the pattern is understood
3. Consider publishing methodology for any scoring, risk, or classification outputs

---

Full programme: https://labs.jamessawyer.co.uk/ai-slop-intelligence-dashboards/