Kronos

Single-source developer blog project with minimal GitHub traction

A personal repository with rank 66 on GitHub but virtually no cross-platform signal. The 'divergence' verdict reflects a single dev.to post (rank 22) driving artificial spread, not organic developer adoption.

Why now: Likely indexed by dev.to search or a single blog post; no event-driven catalyst. GitHub score of 3.8B is raw byte-size or timestamp artifact, not stars/forks, confirming no actual engagement metric.

• Only 2 of 8 weighted sources show any signal (GitHub rank 66, dev.to rank 22)
• Zero presence on HN, X/Twitter, Reddit, Product Hunt, Bluesky despite those being weighted 0.68 combined
• Source count of 2 falls below even 'single_source' threshold in a pool where 160/200 entities are single-source
• Rank gap of 44 between external (69) and ours (92) indicates our pipeline correctly deprioritized it
• dev.to rank 22 with score=1 suggests minimal engagement (likely one post, one view, or search indexing artifact)

Considerations: dev.to rank 22 could indicate an undiscovered technical write-up gaining niche traction. GitHub rank 66 in a 100-row sample is not bottom-tier; some repos with similar profiles later gain momentum through HN or Twitter pickup.

EMERGING SIGNAL · Ignore: No action needed unless it appears on HN front page or gains 50+ GitHub stars in 48 hours.

Sources: GitHub: shiyu-coder/Kronos · dev.to search: shiyu-coder/Kronos