This page lists external signal types the site may consume; deployed instances follow the data pipelines defined in the repository.
| Source | Role | Notes |
|---|---|---|
| GitHub | OSS momentum | Stars, forks, issues/PRs, releases, topics—via REST/GraphQL or public datasets. |
| Public benchmarks | Capability scores | Leaderboards and papers—observe licenses; cite versions and evaluation dates. |
| Preprints & papers | Methods & claims | arXiv and conference papers; note differences vs. final proceedings. |
| Vendor/community releases | Product facts | Model cards, release notes, API docs—mind gaps vs. leaderboard definitions. |
| Internal eval pipelines | Reproducible composites | Private task suites, scoring scripts, CI—pin versions and environments. |
Each published record should retain a snapshot: source URL, fetch time, and a hash or schema version. API throttling or failure requires retry and fallback policies; Methodology should state whether cached values are used and their TTL.
When upstream vendors revise history, maintain a change log or a “last verified” date to avoid stale citations.
Third-party data must comply with terms and rate limits; static pages should use rel="noopener noreferrer" on external links; update this page when licensing changes.