@dfns/lib-vechain
Supply chain provenance
Status for the latest visible version.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Common for internal SDK sub-packages, not indicative of malice. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher is a known prior maintainer, manual publish not a takeover. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): Standard crypto library needed for signing, widely used. | ai | |
| dependencies | unvetted-dep:@vechain/connex-driver | AI (dependencies): Core VeChain SDK dependency matching package purpose. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Small bundled package likely uses it indirectly; not evidence of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Minimal SDK integration library; no description/repo is consistent with the @dfns monorepo pattern across 124 versions. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of ECDSA signature r/s components is standard crypto serialization; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:cross-fetch | AI (phantom-deps): cross-fetch is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is a declared runtime dependency used in bundled output; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.8.20 | 3 / 0 | |
| 0.8.19 | 3 / 0 | |
| 0.8.18 | 3 / 0 | |
| 0.8.17 | 3 / 0 | |
| 0.8.5 | 3 / 0 | |
| 0.8.3 | 3 / 0 | |
| 0.7.18 | 1 / 0 | |
| 0.6.11 | 4 / 0 | |
| 0.6.10 | 4 / 0 | |
| 0.6.9 | 4 / 0 | |
| 0.5.5 | 1 / 0 | |
| 0.5.0 | 4 / 0 | |
| 0.2.0 | 6 / 0 | |
| 0.1.2 | 6 / 0 | |
| 0.1.0 | 0 / 0 |
v0.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (drunkirishcoder) than the most recent previously approved version (thibault2ss) on 2023-12-06, but drunkirishcoder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
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.