How scoring works

What counts as an update

The latest activity is the newest of the public branch build time, any non-public branch build time, and a patch-note or update post. Passworded beta branches still count. If a patch note and a build share the same timestamp, the patch note wins, then the public build, then a beta build.

Steam's own 12-month Early Access notice ignores beta branches. That is how Heartbound was flagged while a beta branch was still moving. This site treats a beta build as activity, and the game page says so when that branch is more than 36 hours newer than public.

Labels

Under 90 days is Actively updated. From 90 days through 180 days is Slowing down. Older than 180 days, or no signal, is Gone quiet. Exactly 90 days is Slowing down. Exactly 180 days is still Slowing down. One hour past 180 days is Gone quiet. List pages recompute the label from the timestamp.

Consistency

Consistency is a 0–100 score of how steadily a game was updated over the last 12 calendar months, including this month, in UTC.

Up to 70 points are coverage: how many of those months contain at least one update day (a unique UTC day with a patch note or a branch build time), divided by 12 and multiplied by 70.

Up to 30 points are regularity: fewer than three update days scores none of them; otherwise the points are 30 times one minus the coefficient of variation of the gaps between those days (the population standard deviation divided by the mean, capped at 1), including the gap from the last update day to today when it is at least one day, and the published score rounds that sum and clamps it from 0 to 100.

• 80–100: Very consistent
• 60–79: Consistent
• 40–59: Irregular
• 20–39: Sporadic
• 0–19: Rarely updated

Lists and game pages show that band first, with a five-segment meter, and keep the number beside it (for example 72/100). PICS returns the current build time on each branch, not a history of older builds. A month can be missed when the only evidence was a build that has since been replaced and no patch note was posted.

AI disclosures

A game is AI-disclosed only when the developer filled in Steam's AI Generated Content Disclosure. appdetails is checked first. If that payload has no field, the store page HTML is parsed. A failed fetch is left unchecked, not marked as non-AI. Developers who never file the form are not flagged. Lists hide these games unless the address includes ai=1.