← Home

claim

npm Repository Homepage

Tiny assertion library

6
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kevvasindresorhus

Keywords

assertassertionerrortesttestingava

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The kevva → sindresorhus transition occurred in 2015 and is a well-documented legitimate handoff. sindresorhus is a highly trusted publisher with thousands of approved packages. ai
maintainer-change maintainer-added AI (maintainer-change): sindresorhus was added as maintainer in 2015 as part of a legitimate transfer. This is a decade-old stable state, not a suspicious recent change. ai
provenance no-provenance AI (provenance): Package was published in 2015, predating Sigstore provenance. No provenance attestation is expected and not a risk signal for this era of publication. ai

Versions (showing 6 of 6)

Version Deps Published
1.4.0 0 / 3
1.3.0 0 / 1
1.2.0 0 / 1
1.1.0 1 / 1
1.0.1 1 / 1
1.0.0 1 / 1

v1.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

2 findings
HIGH Publisher changed: kevva → sindresorhus (on 2015-05-20) provenance

This version was published by a different npm account than previous versions on 2015-05-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

2 findings
HIGH Publisher changed: kevva → sindresorhus (on 2015-05-20) provenance

This version was published by a different npm account than previous versions on 2015-05-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.