Momentum
Change across one-day, seven-day, and thirty-day evidence windows.
PUBLIC METHOD / VERSIONED TRUST
How HeatStack turns signals into a publishable ranking
The ranking is a constrained engineering index, not an editorial mood. Scores, publication gates, freshness states, and historical snapshots follow shared constants used by the product code.
- Published entries
- 50
- Freshness SLA
- 36h
- Minimum quality
- 70
- Maximum risk deduction
- 30
Score composition
Each normalized signal contributes to a 100-point base score. Static risk findings then subtract up to 30 points.
Freshness
How recently the source and its relevant files changed.
Source breadth
Independent source mentions rather than one repeated feed.
Content quality
Readable structure, explicit inputs and outputs, provenance, and bilingual completeness.
HeatStack usage
Observed platform interest such as detail views and package actions, without treating popularity as quality.
What the signals mean
Repository activity and update time describe change; source mentions describe breadth; content structure describes usability; platform usage describes observed HeatStack interest; static risk describes review cost.
Publication gate
A Live ranking is public only when it contains at least 50 public entries. Every entry must be bilingual, enrichment-ready, and have a quality score of at least 70. Hidden entries are not republished from older snapshots.
Tie-breaking
Equal scores are ordered by stable Skill ID, so reruns do not shuffle entries arbitrarily.
Freshness and availability
All generated times are displayed in Asia/Taipei. Every non-fresh state shows total data age; stale data also shows hours past the 36-hour SLA.
live-fresh- API Live ranking whose total age is no more than 36 hours.
live-stale- API Live ranking older than 36 hours; the page shows total age and hours past the SLA.
snapshot-offline- The API is unavailable and the build-time snapshot of the last complete Live ranking is used.
unavailable- Neither the API nor the static snapshot contains a complete verifiable Live ranking.
Historical snapshots
Older real rankings may remain viewable for research and archival search. They must retain their generated time and trust state and must never be described as today's ranking. A build-time snapshot is a recovery view, not a real-time API replacement.