@wzyjs/utils
description
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:node-cron | AI (phantom-deps): Node-only dep in a split-bundle utility package; phantom detection is a false positive here. | ai | |
| phantom-deps | phantom-dep:nedb | AI (phantom-deps): Marked as --external in bun build scripts; not bundled but declared as peer-style dep. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Marked as --external in bun build scripts; not bundled but declared as peer-style dep. | ai | |
| phantom-deps | phantom-dep:papaparse | AI (phantom-deps): Marked as --external in bun build scripts; not bundled but declared as peer-style dep. | ai | |
| phantom-deps | phantom-dep:decimal.js | AI (phantom-deps): Marked as --external in bun build scripts; not bundled but declared as peer-style dep. | ai | |
| phantom-deps | phantom-dep:proxy-agent | AI (phantom-deps): Marked as --external in bun build scripts; not bundled but declared as peer-style dep. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.27 | 22 / 8 | |
| 0.3.22 | 22 / 8 | |
| 0.3.20 | 22 / 8 | |
| 0.3.10 | 22 / 8 | |
| 0.2.74 | 21 / 8 | |
| 0.2.72 | 21 / 8 | |
| 0.2.66 | 21 / 8 | |
| 0.2.65 | 21 / 8 |
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.