G

GitHub Trending

graphify-labs/graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

PythonsurgingLive GitHub sample
View JSON View on GitHub

Current momentum

83capped sample

Stars

129.8K

+0 since sync

Commits

49

in period

Active contributors

12

+0%

Issues closed

6

375.7h avg. resolution

Recorded trajectory

Movement you can verify over time.

Loading daily momentum history.

Behind the number

A score you can inspect.

Each signal contributes points to the total. These are capped GitHub samples, not complete activity counts or proof of adoption.

Development activity40.0 / 40 pts

49 commits · 36 opened PRs · 6 closed issues in 7 days

24 + 22 × ln(1 + weekly weighted activity). Activity = commits + 2 × opened PRs + closed issues. Signal bounded to 0–100, then weighted 40%.

Contributor breadth22.0 / 25 pts

12 sampled contributors in 7 days · 0% contributor-growth input

24 + 25 × ln(1 + contributors × √(7 / days)) + 0.15 × growth. Growth uses the 30-day windows; capped samples use a neutral 0 input. Signal bounded to 0–100, then weighted 25%.

Issue resolution5.6 / 20 pts

375.7 hours resolution input

105 − 9 × log₂(1 + hours). Uses sampled closed issues, not first-response time. With no resolved issues, the model uses 168 hours. Signal bounded to 0–100, then weighted 20%.

Release cadence15.0 / 15 pts

1 days cadence input

105 − 5 × cadence days. With fewer than two published releases, the model uses time since the last push as a proxy. Signal bounded to 0–100, then weighted 15%.

Weighted total · rounded once83 / 100

What changed in the recorded sample?

Loading recorded observations…

12.5K forks

Downstream adoption

1.6K open issues

Community demand

1 day cadence

Shipping consistency