@vates/nbd-client
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:xen-api | AI (dependencies): First-party xen-orchestra ecosystem dep; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:promise-toolbox | AI (dependencies): Well-known utility from the same org; no risk signal. | ai | |
| dependencies | unvetted-dep:@vates/read-chunk | AI (dependencies): First-party @vates scoped dep from the same monorepo. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/log | AI (dependencies): First-party @xen-orchestra scoped dep from the same monorepo. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/async-map | AI (dependencies): First-party @xen-orchestra scoped dep from the same monorepo. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/disk-transform | AI (dependencies): First-party @xen-orchestra scoped dep from the same monorepo. | ai | |
| phantom-deps | phantom-dep:xen-api | AI (phantom-deps): Referenced in config/integration tests, not a real phantom dep risk. | ai | |
| phantom-deps | phantom-dep:@xen-orchestra/async-map | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 7 / 2 | |
| 3.3.0 | 7 / 2 | |
| 3.2.1 | 7 / 2 | |
| 3.1.4 | 6 / 2 | |
| 3.1.3 | 6 / 2 |
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.