@zondax/izari-filecoin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:leb128 | AI (dependencies): leb128 is a standard encoding utility appropriate for a Filecoin library; Filecoin addresses use LEB128 encoding. No malicious signals. | ai | |
| dependencies | unvetted-dep:base32-decode | AI (dependencies): base32-decode is a standard utility appropriate for a Filecoin address library; Filecoin uses Base32 encoding for addresses. No malicious signals. | ai | |
| provenance | no-provenance | AI (provenance): Established Zondax AG package with 13 versions and 3+ year history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.2.6 | 11 / 15 | |
| 1.2.5 | 11 / 15 | |
| 1.2.4 | 11 / 15 | |
| 1.2.3 | 11 / 15 | |
| 1.2.2 | 11 / 15 | |
| 1.2.1 | 11 / 15 | |
| 1.2.0 | 11 / 15 | |
| 1.1.0 | 11 / 15 | |
| 1.0.2 | 11 / 15 | |
| 1.0.1 | 11 / 15 | |
| 1.0.0 | 11 / 15 |
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.