ForgeRank turns public repository signals, bounded Git history, and its own
append-only observations into transparent rankings, momentum, and discovery.
Explore repository intelligence, historical movement, developer evidence, and entire
ecosystems. Every screen is designed around what ForgeRank has actually observed.
ForgeRank / indexed universePUBLIC SIGNALS
Intelligence / six connected views
See reach. See motion. See the engineering beneath both.
01 / MOMENTUM
Popularity is only one axis.
The Momentum Matrix separates observed reach from versioned movement. Real
snapshot windows power every point; incomplete history is withheld rather than
interpolated.
Shareable language, topic, age, and star filters
Logarithmic popularity and fixed 0–100 momentum
Visible cohort and evidence denominators
02 / REPOSITORY DNA
A score you can interrogate.
Repository pages connect score reasons, growth, bounded Git activity, community
structure, detected technology, ranking history, and evidence provenance.
Trending, Rising, Breakout, Most Improved, Hidden Gems, Established, Most Active,
and Cooling Giants remain separate deterministic rankings—not aliases for stars.
Confirmed profiles and explicit non-fork portfolios power transparent developer
views. Git author names are never silently relabeled as public accounts.
Impact Consistency Collaboration
Method / evidence first
Evidence in. Reasons out.
ForgeRank separates acquisition, observation, inference, and presentation. Scores are
versioned; source provenance is retained; missing inputs contribute nothing.
01Identify
Curated identifiers and validated public submissions enter a deduplicated queue.
02Observe
Robots-aware public HTML and bounded Git transport collect allowed evidence.
03Preserve
Append-only snapshots retain timestamps, confidence, parsers, and source hashes.
04Explain
Versioned formulas calculate ranks and persist one reason per score dimension.
0
The defining constraint
No credential-based GitHub path.
No REST API, GraphQL, OAuth, GitHub App, authenticated session, hidden frontend
endpoint, commercial data API, or external embedding service. A repository-wide CI
guard rejects prohibited runtime patterns.
The dimension sum is multiplied by observed confidence. Missing evidence is never
replaced with an industry average.
Repository evidence / current main
Built to survive a clean checkout.
ALL CHECKS
PASSING
PASSQualityFormat · lint · types · build
PASSPostgreSQLReal driver · 22 tables · pg_trgm
PASSBrowser82 desktop/mobile checks
PASSDockerMigrate · seed · readiness · page
PASSPerformance8 optimized-production profiles
PASSDependenciesNo known production vulnerabilities
Local first run
From clone to observatory.
The root runner installs dependencies, migrates the embedded PostgreSQL-compatible
database, loads identifier-only seeds, and starts ForgeRank without GitHub
credentials.
QUICK START
git clone git@github.com:OthmaneBlial/ForgeRank.git
cd ForgeRank
./run.sh
Node.js 22+ · Git 2.40+ · no GitHub token
Honest by construction
A fresh seed contains identifiers, not analytics. Weekly and monthly momentum remain
unavailable until enough real snapshots exist. Rankings describe ForgeRank’s indexed
universe—not every repository on GitHub.
Open source / inspect everything
Discover what matters. Keep the evidence attached.