@ledgerhq/revault-cli
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:asn1js | AI (phantom-deps): CLI tool; asn1js declared as dep, phantom-dep heuristic fires on config references — stable false positive. | ai | |
| phantom-deps | phantom-dep:nanoid | AI (phantom-deps): nanoid declared as dep; phantom-dep heuristic fires on config references — stable false positive. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/revault-api | AI (phantom-deps): Same-org internal dep; phantom-dep heuristic unreliable for monorepo CLI packages. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.21.3 | 18 / 17 | |
| 0.21.2 | 18 / 17 | |
| 0.21.1 | 18 / 17 | |
| 0.21.0 | 18 / 17 | |
| 0.20.7 | 18 / 17 | |
| 0.20.6 | 18 / 17 | |
| 0.20.5 | 18 / 17 | |
| 0.20.4 | 18 / 17 | |
| 0.20.3 | 18 / 17 | |
| 0.20.2 | 18 / 17 | |
| 0.20.1 | 18 / 17 | |
| 0.20.0 | 18 / 17 | |
| 0.19.1 | 18 / 17 | |
| 0.19.0 | 18 / 17 | |
| 0.18.0 | 18 / 17 | |
| 0.17.0 | 18 / 17 | |
| 0.16.1 | 18 / 17 | |
| 0.16.0 | 18 / 17 | |
| 0.15.2 | 18 / 17 | |
| 0.15.1 | 18 / 17 | |
| 0.15.0 | 18 / 17 | |
| 0.14.3 | 18 / 17 | |
| 0.14.2 | 18 / 17 | |
| 0.14.1 | 18 / 17 | |
| 0.14.0 | 18 / 17 | |
| 0.13.4 | 17 / 16 | |
| 0.13.3 | 17 / 16 | |
| 0.13.2 | 17 / 16 | |
| 0.13.1 | 17 / 16 | |
| 0.13.0 | 17 / 16 | |
| 0.12.0 | 17 / 16 | |
| 0.11.3 | 17 / 16 | |
| 0.11.2 | 17 / 16 | |
| 0.11.1 | 17 / 16 | |
| 0.11.0 | 16 / 16 | |
| 0.10.2 | 14 / 16 | |
| 0.10.1 | 14 / 16 | |
| 0.10.0 | 14 / 16 | |
| 0.9.7 | 14 / 16 | |
| 0.9.6 | 14 / 16 | |
| 0.9.5 | 14 / 16 | |
| 0.9.4 | 14 / 16 | |
| 0.9.3 | 14 / 16 | |
| 0.9.2 | 14 / 16 | |
| 0.9.1 | 14 / 16 | |
| 0.9.0 | 14 / 16 | |
| 0.8.10 | 13 / 16 | |
| 0.8.9 | 13 / 16 | |
| 0.8.8 | 13 / 16 | |
| 0.8.7 | 13 / 16 | |
| 0.8.6 | 13 / 16 |
v0.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.