@provex/utils
7
Versions
ISC
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
provexdev
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 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.9.2 | 0 / 4 | |
| 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.9.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.