@provex/utils
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Package has 48 versions, 5k weekly downloads, and a legitimate GitHub repo. Empty description is a quality issue, not a security signal for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm packages lack it); no other signals elevate this to a concern for this package. | ai | |
| phantom-deps | phantom-dep:@zkp2p/providers | AI (phantom-deps): Dependency used in config files but not directly imported is a common monorepo pattern; contextually consistent with this ZK-proof utility package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 1 / 4 | |
| 1.6.2 | 1 / 4 | |
| 1.6.1 | 1 / 4 | |
| 1.3.2 | 1 / 4 | |
| 1.2.3 | 1 / 4 | |
| 1.0.16 | 3 / 1 |
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.