@stdlib/ndarray
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Published by known maintainer kgryte with 246 approved packages; not indicative of account takeover. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects legitimate addition of C kernel source files for new ndarray operations. | ai | |
| source-diff | large-new-source-files | AI (source-diff): 2108 new files are C/header source files for new unary/every ndarray kernels; consistent with stdlib expansion pattern. | ai | |
| dependencies | unvetted-dep:@stdlib/array | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/proxy | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/slice | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/utils | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/assert | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/bigint | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/buffer | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): stdlib-js monorepo consistently publishes without Sigstore provenance; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@stdlib/object | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/string | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/symbol | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/boolean | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/complex | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/constants | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/number | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai | |
| dependencies | unvetted-dep:@stdlib/blas | AI (dependencies): Sibling stdlib monorepo package; trust follows from the established stdlib-js ecosystem. | ai | |
| dependencies | unvetted-dep:@stdlib/math | AI (dependencies): Sibling stdlib monorepo package; stable false positive. | ai |
v0.4.1
2 findings[Accepted risk] Package 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 findings[Accepted risk] Package 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.