Skip to content
Supply chain

Credential Half-Life Scorecard

A worm stole your npm token twenty minutes ago. It is already publishing. Nothing here asks whether you would have caught it — in the August 2026 keyv compromise the malicious packages were correctly signed and passed provenance checks, so detection was not the deciding factor. What decided each victim's blast radius was how long a stolen credential stayed useful. Eight questions, and every one assumes the token is already gone.

Written after the keyv and cacheable compromise — where valid signatures and passing provenance stopped nothing, and credential lifetime decided everything.

Question 1 of 80% complete
Publishing Credentials · This is the credential the worm uses to spread. Its theft harms people downstream of you, not just you.

How long is a package-publishing token (npm, PyPI, crates) valid for?

Loading…

Sample report · illustrative data

Sample result: Credential Half-Life Scorecard

Example answers to the 8 questions (one per domain, each scored 0 to 3) for an invented team, all assuming a publishing token has already been stolen.

Overall

Overall score
50% (12 of 24 points)
Rating
Amber
Weakest domains
CI Credentials, Cloud Keys, Install-Time Execution, Agent & Editor Trust

By domain

DomainScorePercentRating
Publishing Credentials2 / 367%Amber
CI Credentials1 / 333%Red
Cloud Keys1 / 333%Red
Revocation Speed2 / 367%Amber
Blast Radius2 / 367%Amber
Install-Time Execution1 / 333%Red
Agent & Editor Trust1 / 333%Red
Detection of Use2 / 367%Amber

How to read it

Green is 80% or more, Amber 50% to 79%, Red below 50%. It is an indicative self-assessment, not an audit, and it is weighted toward package-publishing and CI credentials rather than a full identity review. The questions ask how long a stolen credential stays useful, not whether you would have prevented the theft.

Made-up example data. Your own run uses your inputs. Downloads of the full report need Pro.

The tools people use most on PlayCISO.

All tools