Skip to content

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

Trending pairings:

A coding-agent skill for multi-phase security audits with independently verified, machine-readable findings

The PHP Interpreter

Side-by-side metrics comparison

Factual figures recorded from the GitHub trending feed and GitHub’s public API without alteration.

Metriccloudflare/security-audit-skillphp/php-src
Stars gained today+2,716+716
Relative growth rate+6.8%+1.8%
Hourly acquisition pace~113.2 stars/h~29.8 stars/h
Total repository stars42,61141,606
Forks2,6588,363
Primary languageJavaScriptC
LicenseMITBSD-3-Clause
Open issues842,235
Last code pushSep 14, 2026Oct 24, 2026
Created on GitHubJun 18, 2026Jun 16, 2011
Install command

Install command found in the README

npx skills add https://github.com/cloudflare/security-audit-skill \
No install command found in README

Traction trajectory

Recorded star history over time as captured by this site’s collector.

Total star trajectory across recorded days
42.6k33.9k25.3kOct 6Oct 7Oct 8Oct 9Oct 10Oct 16Oct 17Oct 18Oct 19Oct 20Oct 21Oct 22Oct 23Oct 24

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 24, 2026, 06:58 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.

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.