@polkadot/react-identicon
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:jdenticon | AI (dependencies): jdenticon is a legitimate identicon library; its use is core to this package's documented functionality. | ai | |
| phantom-deps | phantom-dep:@polkadot/keyring | AI (phantom-deps): Declared as both a dependency and peerDependency; phantom-dep heuristic fires on peer deps for this package consistently. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.16.7 | 10 / 0 | |
| 3.16.4 | 10 / 0 | |
| 3.16.3 | 10 / 0 | |
| 3.16.2 | 10 / 0 | |
| 3.16.1 | 10 / 0 | |
| 3.15.4 | 10 / 0 | |
| 3.15.3 | 10 / 0 | |
| 3.15.2 | 10 / 0 | |
| 3.15.1 | 10 / 0 | |
| 3.14.1 | 10 / 0 |
v3.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.