@ledgerhq/coin-vechain
Ledger VeChain Coin integration
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.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared dependency in package.json; phantom-dep finding is a false positive for this package's build/config structure. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): invariant is a declared dependency in package.json; phantom-dep finding is a false positive for this package's build/config structure. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org package declared as a dependency; phantom-dep finding is a false positive for this monorepo package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(signature, 'hex') is standard hex decoding of a cryptographic signature in a blockchain transaction broadcast — expected and benign for a VeChain coin integration library. | ai |
Versions (showing 71 of 71)
| Version | Deps | Published |
|---|---|---|
| 2.26.0 | 13 / 14 | |
| 2.25.0 | 14 / 14 | |
| 2.24.0 | 14 / 14 | |
| 2.23.0 | 14 / 14 | |
| 2.22.5 | 14 / 14 | |
| 2.22.4 | 14 / 14 | |
| 2.22.3 | 14 / 14 | |
| 2.22.2 | 14 / 14 | |
| 2.22.1 | 14 / 14 | |
| 2.22.0 | 14 / 15 | |
| 2.21.2 | 14 / 15 | |
| 2.21.1 | 14 / 15 | |
| 2.21.0 | 14 / 15 | |
| 2.20.0 | 14 / 15 | |
| 2.19.1 | 14 / 13 | |
| 2.19.0 | 14 / 13 | |
| 2.18.0 | 13 / 13 | |
| 2.17.0 | 13 / 13 | |
| 2.16.6 | 13 / 12 | |
| 2.16.5 | 13 / 12 | |
| 2.16.4 | 13 / 12 | |
| 2.16.3 | 13 / 12 | |
| 2.16.2 | 13 / 12 | |
| 2.16.1 | 13 / 12 | |
| 2.16.0 | 13 / 12 | |
| 2.15.0 | 13 / 11 | |
| 2.14.1 | 13 / 11 | |
| 2.14.0 | 13 / 11 | |
| 2.13.1 | 13 / 11 | |
| 2.13.0 | 13 / 11 | |
| 2.12.1 | 13 / 11 | |
| 2.12.0 | 13 / 11 | |
| 2.11.0 | 13 / 11 | |
| 2.10.1 | 13 / 11 | |
| 2.10.0 | 13 / 11 | |
| 2.9.1 | 12 / 11 | |
| 2.9.0 | 12 / 11 | |
| 2.8.2 | 12 / 11 | |
| 2.8.1 | 12 / 11 | |
| 2.8.0 | 12 / 11 | |
| 2.7.15 | 12 / 12 | |
| 2.7.14 | 12 / 12 | |
| 2.7.13 | 12 / 12 | |
| 2.7.12 | 12 / 12 | |
| 2.7.11 | 12 / 12 | |
| 2.7.10 | 12 / 12 | |
| 2.7.9 | 12 / 12 | |
| 2.7.8 | 12 / 13 | |
| 2.7.7 | 12 / 13 | |
| 2.7.6 | 12 / 13 | |
| 2.7.5 | 12 / 13 | |
| 2.7.4 | 12 / 12 | |
| 2.7.3 | 12 / 12 | |
| 2.7.2 | 12 / 12 | |
| 2.7.1 | 12 / 12 | |
| 2.7.0 | 12 / 12 | |
| 2.6.0 | 12 / 10 | |
| 2.5.1 | 12 / 9 | |
| 2.5.0 | 12 / 9 | |
| 2.4.7 | 12 / 9 | |
| 2.4.6 | 12 / 9 | |
| 2.4.5 | 12 / 9 | |
| 2.4.4 | 12 / 9 | |
| 2.4.3 | 12 / 9 | |
| 2.4.2 | 12 / 9 | |
| 2.4.1 | 12 / 9 | |
| 2.4.0 | 12 / 9 | |
| 2.3.1 | 12 / 9 | |
| 2.3.0 | 12 / 9 | |
| 2.2.1 | 12 / 9 | |
| 2.2.0 | 12 / 9 |
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.