@zondax/zemu
Zemu Testing Framework
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:elfy | AI (dependencies): elfy is a stable ELF-parsing library; its use is appropriate for a Ledger device testing framework. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/errors | AI (phantom-deps): @ledgerhq/errors is a declared runtime dep; likely re-exported or used indirectly in this Ledger testing framework. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.67.4 | 12 / 13 | |
| 0.67.3 | 12 / 13 | |
| 0.67.2 | 12 / 13 | |
| 0.64.1 | 12 / 13 | |
| 0.64.0 | 12 / 13 | |
| 0.63.1 | 12 / 13 | |
| 0.63.0 | 12 / 13 | |
| 0.62.2 | 12 / 13 | |
| 0.62.1 | 12 / 13 | |
| 0.62.0 | 12 / 13 | |
| 0.61.11 | 12 / 13 | |
| 0.61.10 | 12 / 13 | |
| 0.61.4 | 12 / 13 | |
| 0.61.3 | 12 / 13 | |
| 0.61.2 | 12 / 13 | |
| 0.61.1 | 12 / 13 | |
| 0.61.0 | 11 / 13 | |
| 0.60.0 | 11 / 13 |
v0.67.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.67.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.64.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.