← Home

@polkadot-api/ledger-signer

npm Repository Homepage

Ledger libraries require `Buffer` global to exist in scope. If you are on a NodeJS (or Bun) environment you are good to go. If you are on a browser environment, make sure your bundler exposes it or polyfill it yourself with [`buffer` package](https://www.

35
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

volivajosepot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): SLSA provenance attestation present; gitHead absence is inconsequential given Sigstore-backed CI publish. ai
provenance publisher-changed AI (provenance): SLSA attestation confirms CI/CD origin; voliva is an established publisher with 471 approved packages in the polkadot-api org. ai

Versions (showing 35 of 35)

Version Deps Published
0.3.3 5 / 1
0.3.2 5 / 1
0.3.1 5 / 1
0.3.0 5 / 1
0.2.17 5 / 1
0.2.16 5 / 1
0.2.15 5 / 1
0.2.14 5 / 1
0.2.13 5 / 1
0.2.12 5 / 1
0.2.11 5 / 1
0.2.10 5 / 1
0.2.9 5 / 1
0.2.8 5 / 1
0.2.7 5 / 1
0.2.6 5 / 1
0.2.5 5 / 1
0.2.4 5 / 1
0.2.3 5 / 1
0.2.2 5 / 1
0.2.1 5 / 1
0.2.0 5 / 1
0.1.12 5 / 1
0.1.11 5 / 1
0.1.10 5 / 1
0.1.9 5 / 1
0.1.8 5 / 1
0.1.7 5 / 1
0.1.6 5 / 1
0.1.5 5 / 1
0.1.4 4 / 1
0.1.3 4 / 1
0.1.2 4 / 1
0.1.1 4 / 1
0.1.0 4 / 1

v0.1.12

1 finding
LOW No provenance attestation provenance

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

v0.1.11

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. 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. 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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

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.