@keystonehq/sdk
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react-qr-reader | AI (phantom-deps): Type-only convention dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/react-modal | AI (phantom-deps): Type-only convention dep, stable false positive. | ai | |
| phantom-deps | phantom-dep:@types/qrcode.react | AI (phantom-deps): Type-only convention dep, stable false positive. | ai | |
| dependencies | unvetted-dep:@types/qrcode.react | AI (dependencies): Type-only dep, benign. | ai | |
| dependencies | unvetted-dep:@types/react-qr-reader | AI (dependencies): Type-only dep, benign. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): Type-only convention dep, stable false positive. | ai | |
| dependencies | unvetted-dep:react-qr-reader | AI (dependencies): Popular, legitimate QR reader lib; long-standing dependency of this SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established KeystoneHQ package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.22.1 | 5 / 13 | |
| 0.22.0 | 5 / 13 | |
| 0.21.3 | 5 / 13 | |
| 0.21.2 | 5 / 13 | |
| 0.21.1 | 5 / 13 | |
| 0.20.0 | 5 / 14 | |
| 0.7.1 | 11 / 0 | |
| 0.1.0 | 11 / 0 |
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.