← Home

@polkadot-api/polkadot-signer

npm Repository Homepage
9
Versions
—
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

volivajosepot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@polkadot-api/utils AI (phantom-deps): Same-org monorepo dependency; common pattern where transitive/peer deps are declared but not directly imported. ai
phantom-deps phantom-dep:@polkadot-api/metadata-builders AI (phantom-deps): Same-org monorepo dependency; common pattern where transitive/peer deps are declared but not directly imported. ai
phantom-deps phantom-dep:@polkadot-api/substrate-bindings AI (phantom-deps): Same-org monorepo dependency; common pattern where transitive/peer deps are declared but not directly imported. ai
bogus-package bogus-package AI (bogus-package): This is a legitimate types/interface package from the polkadot-api monorepo. Minimal metadata and tiny payload are expected for this kind of scoped utility package. ai
npm-metadata no-description AI (npm-metadata): Established polkadot-api monorepo package; missing description is a cosmetic issue, not a malice indicator. ai

Versions (showing 9 of 9)

Version Deps Published
0.1.6 0 / 0
0.1.5 0 / 0
0.1.4 0 / 0
0.1.3 3 / 0
0.1.2 3 / 0
0.1.1 3 / 0
0.1.0 3 / 0
0.0.2 3 / 0
0.0.1 3 / 0

v0.1.6

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

v0.1.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.1.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.0.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.

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