@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, so a manually published version cannot be tied back to a reviewed commit.
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 9 of 9)
| 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 | |
| 3.1.2 | 6 / 2 | |
| 3.1.1 | 6 / 2 | |
| 3.1.0 | 6 / 2 | |
| 3.0.2 | 6 / 2 |
v3.1.2
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 (florent.beauchamp) than the most recent previously approved version (b-nollet) on 2024-11-07, but florent.beauchamp 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.
v3.1.1
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 (b-nollet) than the most recent previously approved version (mlssfrncjrg) on 2024-10-28, but b-nollet 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.
v3.1.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 (b-nollet) than the most recent previously approved version (mlssfrncjrg) on 2024-07-25, but b-nollet 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.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.