← Home

@parity/hardhat-polkadot-resolc

npm Repository Homepage

Polkadot [Hardhat](https://hardhat.org/) plugin to compile Ethereum-compatible solidity smart contracts.

12
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript is a declared dep used by the build toolchain; stable false positive for this TS plugin. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Framework-scoped type package; stable false positive for TypeScript packages. ai
phantom-deps phantom-dep:@types/debug AI (phantom-deps): Framework-scoped type package; stable false positive for TypeScript packages. ai
phantom-deps phantom-dep:find-up AI (phantom-deps): Listed as runtime dep in package.json; used transitively or in config; stable false positive for this package. ai
phantom-deps phantom-dep:ts-node AI (phantom-deps): Listed as runtime dep; used for TypeScript config execution; stable false positive for this package. ai
phantom-deps phantom-dep:@ethereumjs/util AI (phantom-deps): Listed as runtime dep; used transitively or in config; stable false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
0.2.4 9 / 10
0.2.3 9 / 10
0.2.2 9 / 10
0.2.1 10 / 10
0.2.0 10 / 10
0.1.8 10 / 10
0.1.7 13 / 7
0.1.6 8 / 6
0.1.5 8 / 6
0.1.4 8 / 6
0.1.3 7 / 5
0.1.2 8 / 5

v0.2.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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.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.

v0.1.2

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.