@polkadot-api/pjs-signer
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; missing gitHead is superseded by stronger CI/CD integrity signal. | ai | |
| provenance | publisher-changed | AI (provenance): voliva is a trusted publisher (472 approved, 0 rejected) within the polkadot-api org; legitimate maintainer transition. | ai | |
| phantom-deps | phantom-dep:@polkadot-api/metadata-builders | AI (phantom-deps): Same org scope; likely used transitively or in type declarations rather than direct import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is typical for monorepo sub-packages; not indicative of malicious intent. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.21 | 5 / 0 | |
| 0.6.20 | 5 / 0 | |
| 0.6.19 | 5 / 0 | |
| 0.6.18 | 5 / 0 | |
| 0.6.17 | 5 / 0 | |
| 0.6.16 | 5 / 0 | |
| 0.6.15 | 5 / 0 | |
| 0.6.14 | 5 / 0 | |
| 0.6.13 | 5 / 0 | |
| 0.6.12 | 5 / 0 | |
| 0.6.11 | 5 / 0 | |
| 0.6.10 | 5 / 0 | |
| 0.6.9 | 5 / 0 | |
| 0.6.8 | 5 / 0 | |
| 0.6.7 | 5 / 0 | |
| 0.6.6 | 5 / 0 | |
| 0.6.5 | 5 / 0 | |
| 0.6.4 | 5 / 0 | |
| 0.6.3 | 5 / 0 | |
| 0.6.2 | 5 / 0 | |
| 0.6.1 | 5 / 0 | |
| 0.6.0 | 5 / 0 | |
| 0.5.2 | 5 / 0 | |
| 0.5.1 | 5 / 0 | |
| 0.5.0 | 4 / 0 | |
| 0.4.5 | 4 / 0 | |
| 0.4.4 | 4 / 0 | |
| 0.4.3 | 4 / 0 | |
| 0.4.2 | 4 / 0 | |
| 0.4.1 | 4 / 0 | |
| 0.4.0 | 4 / 0 | |
| 0.3.2 | 4 / 0 | |
| 0.3.1 | 4 / 0 | |
| 0.3.0 | 4 / 0 | |
| 0.2.1 | 4 / 0 | |
| 0.2.0 | 4 / 0 | |
| 0.1.4 | 4 / 0 | |
| 0.1.3 | 4 / 0 | |
| 0.1.2 | 4 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 4 / 0 | |
| 0.0.1 | 4 / 0 |
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.