@wbce-d9/utils
2
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
louis75delo06260
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): tmp is declared as a runtime dep and used in node utilities; phantom-dep heuristic fires on config-only reference, not a real concern. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): vue is a peer/browser-side dep referenced in config; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@wbce-d9/storage | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on config reference, stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README is typical for internal monorepo utility packages; not indicative of spam or malice. | ai |
v10.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.
v10.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.