Compare trending repositories side by side
Evaluate GitHub trending projects across star momentum, relative growth, license, maintenance activity and recorded traction history.
Collected
Choose repositories to compare
A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings
OpenShell is the safe, private runtime for autonomous AI agents.
Side-by-side metrics comparison
Factual figures recorded from the GitHub trending feed and GitHub’s public API without alteration.
| Metric | cloudflare/security-audit-skill | NVIDIA/OpenShell |
|---|---|---|
| Stars gained today | +2,264 | +896 |
| Relative growth rate | +5.3% | +4.8% |
| Hourly acquisition pace | ~94.3 stars/h | ~37.3 stars/h |
| Total repository stars | 45,199 | 19,625 |
| Forks | 2,806 | 1,940 |
| Primary language | JavaScript | Rust |
| License | MIT | Apache-2.0 |
| Open issues | 90 | 579 |
| Last code push | Sep 14, 2026 | Oct 24, 2026 |
| Created on GitHub | Jun 18, 2026 | Feb 24, 2026 |
| Install command | Install command found in the README npx skills add https://github.com/cloudflare/security-audit-skill \ | Install command found in the README npx skills add NVIDIA/OpenShell |
Traction trajectory
Recorded star history over time as captured by this site’s collector.
Drawn using UTC daily readings recorded by this site’s collector. If a repository has fewer plotted points, it joined the trending lists more recently.
Comparative figures reflect public readings from github.com/trending and GitHub REST API metadata at Oct 25, 2026, 06:56 UTC.
Source: github.com/trending · updated
Why use this instead of the GitHub page
- Every list says when it was read
- The collection time is printed above each list, and a warning appears when it is more than 24 hours old. A list is never shown as “today” without its date.
- The ranking is GitHub’s, not ours
- Positions and “stars today” are copied from github.com/trending. There is no hidden score; the method page describes each number.
- A page for every day
- The daily list is stored under its date in the archive, so yesterday’s ranking does not disappear when today’s replaces it.
- Install command only when one exists
- The command box appears only when the README contains a real install line that names the project. No generic “git clone” on every card.
- Filters you can link to
- Search text, language, topic, sort order and view are written to the address, so a link reproduces exactly what you see.
- Feeds for readers and scripts
- The daily list, languages and topics have their own RSS and JSON feeds, with the same collection time on every item.
More lists to explore
The same data cut by period, programming language and subject.
By period
By language, today
By subject
Questions and answers
More detail on the method page.
How does the side-by-side comparison work?
Select any two trending repositories from today’s collection or the archive. The tool matches their recorded metrics—GitHub rank, stars gained today, relative growth percentage, total stars, forks, open issues, SPDX license, push date, and install command—into an aligned comparison matrix.
How is relative growth calculated in the comparison?
Relative growth divides stars gained in the period by the repository’s starting star count prior to the period (total stars minus stars gained). It measures how quickly a repository is expanding relative to its existing baseline rather than absolute star count alone.
What does hourly star velocity tell you?
Hourly velocity divides the 24-hour star gain by 24. While GitHub updates its trending counts periodically rather than by the minute, this uniform rate lets you benchmark acquisition speed across projects of differing sizes.
Can I share a comparison with a colleague?
Yes. Selecting repositories updates the query parameters in the page address (such as ?a=owner/repo1&b=owner/repo2). Anyone opening that link sees the exact same side-by-side comparison and traction chart.
Why do some repositories have longer traction charts than others?
Our collector records daily star readings for repositories while they appear on GitHub’s trending lists. Projects that have trended across multiple archive days accumulate longer historical curves in our dataset.