@zeroclickai/paywrap
Framework-agnostic primitives for building agent-callable paid APIs over HTTP: MPP/x402 gates, pricing manifests, credential verification, and settlement logs.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Young package without CI provenance setup; no other risk signals present. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.0.22 | 4 / 4 | |
| 0.0.19 | 4 / 4 | |
| 0.0.15 | 4 / 4 | |
| 0.0.14 | 4 / 4 | |
| 0.0.13 | 4 / 4 | |
| 0.0.12 | 4 / 4 | |
| 0.0.7 | 4 / 4 | |
| 0.0.6 | 4 / 4 | |
| 0.0.5 | 4 / 4 | |
| 0.0.4 | 4 / 4 | |
| 0.0.3 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v0.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.19
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anthony-zeroclick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anthony-zeroclick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anthony-zeroclick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anthony-zeroclick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anthony-zeroclick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.