← Home

better-assert

npm Repository Homepage

Better assertions for node, reporting the expr, filename, lineno etc

5
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tjholowaychuktony_ado

Keywords

assertstacktracedebug

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition from tjholowaychuk to tony_ado (a listed contributor) in 2014; tony_ado has clean 12-year track record. ai
maintainer-change maintainer-added AI (maintainer-change): tony_ado is a listed contributor; this was a legitimate handoff from TJ Holowaychuk circa 2014. ai

Versions (showing 5 of 5)

Version Deps Published
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0
0.1.0 1 / 0
0.0.1 1 / 0

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

2 findings
HIGH Publisher changed: tjholowaychuk → tony_ado (on 2014-07-23) provenance

This version was published by a different npm account than previous versions on 2014-07-23. 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.0

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.