@stdlib/assert
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in is-browser detection to check global scope; well-known safe pattern in this stdlib package. | ai | |
| phantom-deps | phantom-dep:@stdlib/cli | AI (phantom-deps): Same-org stdlib sub-package; phantom-dep heuristic is unreliable for monorepo-style packages. | ai | |
| phantom-deps | phantom-dep:@stdlib/process | AI (phantom-deps): Same-org stdlib sub-package; phantom-dep heuristic is unreliable for monorepo-style packages. | ai |
v0.4.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kgryte) than the most recent previously approved version (stdlib-bot) on 2026-06-05, but kgryte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kgryte) than the most recent previously approved version (stdlib-bot) on 2026-06-05, but kgryte is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.