@parity/hardhat-polkadot-node
Polkadot [Hardhat](https://hardhat.org/) plugin to run a mock in-memory node.
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:@types/fs-extra | AI (phantom-deps): Framework-scoped @types package; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): TypeScript compiler dependency; used by build toolchain, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; loaded by convention in Node.js TS projects. | ai | |
| phantom-deps | phantom-dep:@types/debug | AI (phantom-deps): Type-only package for debug; loaded by convention, not directly imported. | ai | |
| phantom-deps | phantom-dep:@types/mocha | AI (phantom-deps): Type-only package for mocha; loaded by convention in test setups. | ai | |
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is a declared runtime dep used in config/tooling context; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 11 / 13 | |
| 0.2.4 | 11 / 13 | |
| 0.2.0 | 11 / 13 | |
| 0.1.5 | 11 / 13 | |
| 0.1.4 | 12 / 9 | |
| 0.1.3 | 12 / 8 | |
| 0.1.1 | 9 / 6 |
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.4
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
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.