@keystonehq/keystone-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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party keystonehq scoped BC-UR registry package, consistent with existing deps. | ai | |
| provenance | missing-githead | AI (provenance): Explained by known-maintainer manual publish, not a hijack indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established SDK package; sparse README/keywords are typical for this org's packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals elevate this. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 25 / 16 | |
| 0.12.2 | 25 / 16 | |
| 0.12.1 | 25 / 16 | |
| 0.12.0 | 25 / 16 | |
| 0.11.7 | 25 / 16 | |
| 0.11.6 | 25 / 16 | |
| 0.11.5 | 24 / 16 | |
| 0.11.4 | 24 / 16 | |
| 0.11.3 | 24 / 16 | |
| 0.11.2 | 24 / 16 | |
| 0.11.1 | 24 / 16 | |
| 0.11.0 | 24 / 16 | |
| 0.10.1 | 23 / 16 | |
| 0.10.0 | 23 / 16 | |
| 0.9.3 | 23 / 16 | |
| 0.9.2 | 21 / 16 | |
| 0.9.1 | 21 / 16 | |
| 0.9.0 | 21 / 16 | |
| 0.8.1 | 20 / 16 | |
| 0.8.0 | 20 / 16 | |
| 0.7.9 | 20 / 16 | |
| 0.7.8 | 20 / 16 | |
| 0.7.7 | 20 / 16 | |
| 0.7.6 | 20 / 16 | |
| 0.7.5 | 20 / 16 | |
| 0.7.3 | 20 / 16 | |
| 0.7.2 | 20 / 16 | |
| 0.7.1 | 20 / 16 | |
| 0.7.0 | 20 / 16 | |
| 0.6.0 | 20 / 16 | |
| 0.5.1 | 19 / 16 | |
| 0.5.0 | 19 / 16 | |
| 0.4.1 | 19 / 16 | |
| 0.4.0 | 19 / 16 | |
| 0.3.0 | 18 / 16 | |
| 0.2.6 | 17 / 16 | |
| 0.2.5 | 17 / 16 | |
| 0.2.4 | 17 / 16 | |
| 0.2.3 | 17 / 16 | |
| 0.2.2 | 16 / 16 | |
| 0.2.1 | 16 / 16 | |
| 0.2.0 | 16 / 16 | |
| 0.1.8 | 16 / 16 | |
| 0.1.7 | 16 / 16 | |
| 0.1.6 | 16 / 16 | |
| 0.1.5 | 15 / 16 | |
| 0.1.4 | 16 / 16 | |
| 0.1.3 | 16 / 16 | |
| 0.1.2 | 12 / 16 | |
| 0.1.1 | 12 / 16 | |
| 0.1.0 | 12 / 16 | |
| 0.0.1 | 11 / 17 |
v0.10.0
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: soralit.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
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: soralit.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
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: soralit.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
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: soralit.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (soralit) than the most recent previously approved version (liyanlance) on 2024-10-23, but soralit is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.8.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-08-12, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-07-26, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-07-26, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.7
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-07-17, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-07-16, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-07-09, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (liyanlance) on 2024-06-26, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liyanlance) than the most recent previously approved version (soralit) on 2024-06-18, but liyanlance is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.6.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: keystoneorg.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (keystoneorg) than the most recent previously approved version (soralit) on 2024-05-31, but keystoneorg is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liyanlance) than the most recent previously approved version (soralit) on 2024-05-23, but liyanlance is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.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.4.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.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (liyanlance) than the most recent previously approved version (amalia20220301) on 2023-07-13, but liyanlance is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (amalia20220301) than the most recent previously approved version (liyanlance) on 2023-07-12, but amalia20220301 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.