@blocklet/payment-react-headless
Headless React hooks for payment-kit checkout
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): ArcBlock monorepo package; no provenance is consistent across all versions of this package family. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.28.0 | 9 / 9 | |
| 1.27.2 | 9 / 9 | |
| 1.27.1 | 9 / 9 | |
| 1.27.0 | 9 / 9 | |
| 1.26.5 | 9 / 9 | |
| 1.26.4 | 9 / 9 | |
| 1.26.3 | 9 / 9 | |
| 1.26.2 | 9 / 9 | |
| 1.26.1 | 9 / 9 | |
| 1.26.0 | 9 / 9 |
v1.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.