START SYSTEM_PROMPTS_LEAKS'S PERMANENT RECORD
system_prompts_leaks sits #599 of every public repository, climbing 253★/day and ~17d from the top 500. Right now that is a snapshot. The hour-by-hour record of how it got here, and where it is heading, only exists from the moment you start charting it.
GITHUB IS ERASING YOUR EVIDENCE
two clocks running against youGitHub deletes your traffic — clones, views and referrers — every 14 days, and star history cannot be backfilled. The forensic truth about system_prompts_leaks only exists from the day tracking starts. system_prompts_leaks added ~1,771 stars in the last 7 days alone — none of it on a record yet.
THIS IS WHAT TRACKING SYSTEM_PROMPTS_LEAKS LOOKS LIKE
no mockups · real dataWe have been recording system_prompts_leaks's world rank for 3 days. Tracking unlocks every point, keeps every day from here, and you never lose another. This is the one thing that cannot be backfilled.
CHOOSE YOUR MISSION
cancel anytime · your history stays yours- ◆Run the full system_prompts_leaks console yourself: chart, replay, the race
- ◆MIT template, deploy on your own Vercel in ~5 min
- ◆Or just keep the free public snapshot of system_prompts_leaks you see now
- ◆Exact hourly history of system_prompts_leaks from the second you pay (it cannot be backfilled)
- ◆system_prompts_leaks's full console unlocked: rank trajectory, daily ladder, heatmap, spike forensics
- ◆Who's hunting system_prompts_leaks: live gaps and ETAs on Fabric and Alamofire, and every repo closing in
- ◆Traffic Vault: system_prompts_leaks's clones, views and referrers, kept past GitHub's 14-day wipe
- ◆Exact live star counter on system_prompts_leaks's README badge and embed
- ◆Alerts the moment a hunter closes in or system_prompts_leaks breaks into the top 500 (Slack, Discord, RSS)
- ◆Everything in Pro, across up to 10 of asgeirtj's repos
- ◆3 seats — the whole fleet on one wall
- ◆Slack & webhook alerts for the team
- ◆Priority support
- ◆Everything in Team, across up to 30 of asgeirtj's repos
- ◆SSO and centralized billing
- ◆Your entire open-source portfolio, tracked
- ◆A direct line for the features you need
THE DATA IS NEVER FOR SALE. Paying never moves a pixel of system_prompts_leaks's chart, or anyone's. You buy the operation and your own history — never position.
STRAIGHT ANSWERS
Can't I just self-host it for free?
Yes — it is MIT and deploys in about five minutes. You run the collector, manage the GitHub quota and keep it alive. Hosted is the same product with zero ops, and it starts recording the second you click, not the day you finish a deploy.
Why can't you backfill my history?
GitHub caps how far back its API goes, and the public archives miss viral bursts. The hour-by-hour truth of how a repo grew only exists from the moment tracking starts. Every day you wait is gone for good.
Do you sell my data, or move my position?
Never. It is public GitHub data, never for sale, and paying never moves a single pixel of any chart — not yours, not anyone's. You buy the operation and your own record, never position.
Can I cancel? Is the history mine?
Cancel anytime. Every day you recorded is yours to export and keep — paying buys the operation, not a hostage.
Who pays — me, or my employer?
Team and Business are built for the company to pay. A maintainer should never pay out of pocket to track the repo they keep alive for their employer.
NOT A CUSTOMER, A PATRON?
If you just want the public telemetry to stay free and independent, that path exists too: sponsorship funds the mission and buys exactly zero influence.
BECOME A MISSION PATRON · from $5/mo →