ninjahawk /livenerf
Benchmark for tracking model capability after release.
- Stars
- 1,705 stars
- Forks
- 22 forks
- Language
- Python
- License
- MIT
- Created
- Sep 22, 2026
- Last push
- Nov 5, 2026
- Updated
- Nov 5, 2026
Why these Tags: an agent read the README and quoted it
- LLM evaluation from the readme:
A long-running, deterministic-as-possible benchmark for detecting whether a frontier model gets quietly worse after launch.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an errorwith the form at the end of this page.
Admitted to the Repository Index on Nov 4, 2026: +100 stars in 7 days.
Star History
45 days recorded, Sep 22, 2026 – Nov 5, 2026 (UTC). Net change +1,707 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour. Add ?theme=light or ?theme=darkto the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/ninjahawk/livenerf)Badge
[](https://awesomerepos.com/ninjahawk/livenerf)Timeline
It gained stars on each of the 45 days recorded since Sep 22, 2026.
Its largest 7 days were Sep 27, 2026 to Oct 3, 2026: 1,162 stars.
- Created on the Repository Host
- Reached 100 stars, 5 days after it was created
- +310 stars in one day
- Reached 500 stars, 8 days after it was created
- Largest star day recorded: +429 stars
- Reached 1,000 stars, 9 days after it was created
- +200 stars in one day
- Entered the Repository Index: +100 stars in 7 days
- Latest push
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 2 Observations, Nov 5, 2026 – Nov 6, 2026. Forks +1. AwesomeRepos saw a new push on 1 of 1 days.
- Nov 6, 2026: new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check
Maintenance
2 of 4 checks (2 without data)Yes: Not archived
GitHub does not mark the repository as archived. Source
Yes: A push in the last 90 days
Last push on 2026-11-05, 0 days ago. Source
No data: Commits in the last 13 weeks
No data: AwesomeRepos has not read the weekly commits.
No data: Commits in 26 or more of the last 52 weeks
No data: AwesomeRepos has not read the weekly commits.
Releases
0 of 3 checks (2 without data)No: A release in the last 365 days
No GitHub release (read on 2026-11-06). Source
No data: The newest release tag is a semantic version
No data: no release.
No data: A changelog file at the root
No data: AwesomeRepos has not scanned this repository.
Security practice
0 of 1 check (1 without data)No data: A security policy
No data: AwesomeRepos has not scanned this repository.
AwesomeRepos has not asked OpenSSF Scorecard about this repository.
Community files
1 of 3 checks (2 without data)Yes: A licence
GitHub finds the licence MIT. Source
No data: A contributing guide
No data: AwesomeRepos has not scanned this repository.
No data: A code of conduct
No data: AwesomeRepos has not scanned this repository.
Dependencies in the index
This section shows the packages that connect this repository to other repositories in the index.
GitHub has no dependency graph for this repository (scanned on Nov 6, 2026).
No scanned repository names a package from this repository.
Uses (in the index) · 0
None.
Used by (in the index) · 0
None.
Sources: the GitHub dependency graph of each repository, and deps.dev for the source repository of each package. A dependency graph also names development packages. deps.dev takes most source repositories from package metadata. How the dependency graph is made
Observations
Latest Observation, Nov 6, 2026: 1,705 stars, 22 forks, last push Nov 5, 2026, not archived. One of 2 Observations since Nov 5, 2026.