@keystonehq/bc-ur-registry
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher matched as known prior maintainer; provenance analyzer confirms manual publish by known account. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): bs58check replaces base58check, a like-for-like well-known encoding lib swap. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit runtime dep, not a real gap. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): All hex-decode hits are hardcoded BIP-32/BIP-44 constant bytes, not dynamic payload decoding. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 3 / 30 | |
| 0.7.1 | 3 / 30 | |
| 0.7.0 | 3 / 30 | |
| 0.6.4 | 3 / 30 | |
| 0.6.3 | 3 / 30 | |
| 0.6.2 | 3 / 30 | |
| 0.6.1 | 3 / 30 | |
| 0.6.0 | 3 / 29 | |
| 0.5.5 | 3 / 30 | |
| 0.5.4 | 3 / 30 | |
| 0.5.3 | 3 / 30 | |
| 0.5.2 | 3 / 30 | |
| 0.5.1 | 3 / 30 | |
| 0.5.0 | 3 / 27 | |
| 0.4.4 | 3 / 26 | |
| 0.4.3 | 3 / 26 | |
| 0.4.2 | 3 / 26 | |
| 0.4.1 | 2 / 26 | |
| 0.4.0 | 2 / 26 | |
| 0.3.1 | 2 / 24 | |
| 0.3.0 | 2 / 20 | |
| 0.2.0 | 2 / 20 | |
| 0.1.1 | 2 / 13 | |
| 0.1.0 | 2 / 13 |
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
2 findingsThis version was published by a different npm account (liyanlance) than the most recent previously approved version (keystoneorg) on 2023-09-28. It has since remained available on npm for 1027 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
2 findingsThis version was published by a different npm account (liyanlance) than the most recent previously approved version (keystoneorg) on 2023-06-07. It has since remained available on npm for 1141 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
2 findingsThis version was published by a different npm account (liyanlance) than the most recent previously approved version (keystoneorg) on 2023-06-07. It has since remained available on npm for 1141 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
2 findingsThis version was published by a different npm account (liyanlance) than the most recent previously approved version (keystoneorg) on 2023-06-07. It has since remained available on npm for 1141 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
2 findingsPackage 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 (keystoneorg) on 2023-05-31, 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.5.5
2 findingsThis version was published by a different npm account (liyanlance) than the most recent previously approved version (keystoneorg) on 2023-04-27. It has since remained available on npm for 1182 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsPackage 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 (keystoneorg) on 2022-12-21, 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.5.3
2 findingsPackage 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 (keystoneorg) on 2022-11-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.5.2
2 findingsPackage 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 (keystoneorg) on 2022-11-15, 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.5.1
2 findingsPackage 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 (keystoneorg) on 2022-11-03, 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.5.0
2 findingsThis version was published by a different npm account (amalia20220301) than the most recent previously approved version (keystoneorg) on 2022-07-28. It has since remained available on npm for 1454 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
2 findingsPackage 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 (keystoneorg) on 2021-07-22, 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.4.2
2 findingsPackage 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 2021-07-21, 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.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.