@polkadot-labs/hdkd
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 | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is consistent with legitimate automation; SLSA attestation confirms CI provenance. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI-published release with SLSA attestation and no code changes; low takeover risk. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA provenance via Sigstore is a strong supply chain integrity signal; stable for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 0.0.29 | 1 / 7 | |
| 0.0.28 | 1 / 7 | |
| 0.0.27 | 1 / 7 | |
| 0.0.26 | 1 / 7 | |
| 0.0.25 | 1 / 7 | |
| 0.0.24 | 1 / 7 | |
| 0.0.23 | 1 / 7 | |
| 0.0.22 | 1 / 7 | |
| 0.0.21 | 1 / 7 | |
| 0.0.20 | 1 / 7 | |
| 0.0.19 | 1 / 7 | |
| 0.0.18 | 1 / 7 | |
| 0.0.17 | 1 / 7 | |
| 0.0.16 | 1 / 7 | |
| 0.0.15 | 1 / 7 | |
| 0.0.14 | 1 / 7 | |
| 0.0.13 | 1 / 7 | |
| 0.0.12 | 1 / 7 | |
| 0.0.11 | 1 / 7 | |
| 0.0.10 | 1 / 6 | |
| 0.0.9 | 1 / 6 | |
| 0.0.8 | 2 / 6 | |
| 0.0.7 | 2 / 6 |
v0.0.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.