← Home

@parity/hardhat-polkadot

npm Repository Homepage

Use Hardhat with Polkadot all-in-one plugin

13
Versions
AGPL-3.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

parity-jacogrjacogrparitytechkianenigmawirednkoddvdplmmcornholioparitytech-cinachopalparitypepostefan-sopicvincecorsica

Keywords

ethereumsmart-contractshardhathardhat-pluginpolkadot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): All raw-IP references are localhost (127.0.0.1) in sample project hardhat configs — not network exfiltration. ai
phantom-deps phantom-dep:semver AI (phantom-deps): semver is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:jscodeshift AI (phantom-deps): jscodeshift is a declared runtime dep used in migrator tooling; false positive for this package. ai
phantom-deps phantom-dep:@openzeppelin/contracts AI (phantom-deps): Declared dep bundled for sample projects; phantom-dep heuristic false positive here. ai

Versions (showing 13 of 13)

Version Deps Published
0.3.0 13 / 16
0.2.3 13 / 16
0.2.2 13 / 16
0.2.1 13 / 16
0.2.0 13 / 16
0.1.10 7 / 13
0.1.9 7 / 13
0.1.8 7 / 13
0.1.7 7 / 13
0.1.6 7 / 13
0.1.5 6 / 12
0.1.4 6 / 12
0.1.3 6 / 12

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.