Methodology

Not all data points carry equal weight. We apply minimum thresholds to flag low-confidence signals:

Each company receives a 0–100 data confidence score reflecting profile completeness, identifier verification, metric freshness, and signal coverage.

• Download inflation: CI/CD pipelines can inflate package download counts through automated builds.
• Private registries excluded: Downloads from private npm/PyPI registries aren't counted. Enterprise usage is underrepresented.
• Package mapping is manual: Some companies may have packages we haven't linked yet.
• HN sentiment is directional: Sentiment classification works best with 30+ comments. Smaller samples are shown with lower confidence.
• Commit velocity is a proxy: More commits doesn't mean more features. Spikes may reflect refactoring, docs, or bug fixes.
• Closed-source blind spots: Companies without public GitHub repos or published packages have fewer trackable signals.

Funding rounds are detected from news feeds (TechCrunch, VentureBeat) and cross-referenced against company announcements and Wikipedia. Every round is manually verified before appearing on a company profile. We'd rather miss a round than publish incorrect data.

Every data point goes through a 4-layer validation pipeline:

1. Integrity checks - 18 automated checks verify data constraints, completeness, and cross-field consistency on every sync.
2. External source verification - GitHub repos, npm/PyPI packages, and company websites are cross-checked against live APIs to detect stale or incorrect identifiers.
3. Anomaly detection - Time-series monitoring flags unusual metric changes (e.g., sudden drops in GitHub stars or download spikes) for manual review.
4. Confidence scoring - Each company receives a 0-100 data confidence score based on profile completeness, identifier verification, metric freshness, and signal computation coverage.

Found an error? Use the "Report an error" button on any company profile, and we'll review it promptly.

The Developer Momentum Index combines all the signals described above into a single composite score (0-100) for each company. It weights developer adoption, community discussion, momentum trends, and search demand to rank AI companies by real developer traction.

For a detailed explanation of how the DMI is calculated, score tiers, and limitations, see the Developer Momentum Index page.

The momentum score (0–100) measures how quickly a company is gaining or losing developer traction. It combines four directional components:

Confidence Weighting

Not every company has data for all four components. When components are missing, the available weights redistribute proportionally so the score still uses the full 0–100 range. A confidence value (0.25–1.0) records the fraction of components that were available:

• 1.0 — all 4 components present
• 0.75 — 3 of 4
• 0.5 — 2 of 4
• 0.25 — 1 of 4

When the momentum score feeds into the signal score, it is multiplied by this confidence value, so companies with fewer data points receive proportionally less credit.

The signal score (used for ranking and prioritization) includes demand-side metrics that capture real user interest. These account for 40% of the total signal score:

The remaining 60% of the signal score comes from supply-side signals (HN mentions, GitHub stars, momentum, funding recency — 40%) and data quality (profile coverage, package downloads — 20%).

When demand data is unavailable (e.g., a newly added company with no page views yet), the demand components gracefully degrade to 0 rather than penalizing the company. This means the score is driven entirely by supply-side and data quality signals until demand data becomes available.