@polkadot-apps/keys
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@polkadot-labs/hdkd-helpers | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo sub-package from paritytech-ci; sparse metadata is expected for org-scoped utility packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with internal monorepo package pattern from trusted publisher. | ai | |
| phantom-deps | phantom-dep:polkadot-api | AI (phantom-deps): Likely used in config/type files only; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@polkadot-labs/hdkd | AI (phantom-deps): Config-file reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@polkadot-apps/crypto | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@polkadot-apps/address | AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): paritytech-ci is a trusted publisher; absence of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.4.4 | 7 / 1 | |
| 0.4.3 | 7 / 1 | |
| 0.4.2 | 7 / 1 | |
| 0.4.1 | 7 / 1 | |
| 0.4.0 | 7 / 1 | |
| 0.3.8 | 7 / 1 | |
| 0.3.7 | 7 / 1 | |
| 0.3.6 | 7 / 1 | |
| 0.3.5 | 7 / 1 | |
| 0.3.4 | 6 / 1 | |
| 0.3.3 | 6 / 1 | |
| 0.3.2 | 6 / 1 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.2.0 | 5 / 1 |
v0.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.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.3.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.2.2
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.