xen-api
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has 101/0 approval history; likely legitimate org maintainer rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Consistent with monorepo maintainer rotation, same publisher vetted elsewhere. | ai | |
| dependencies | unvetted-dep:xo-common | AI (dependencies): Same-org (vatesfr/xen-orchestra) package; stable false positive. | ai | |
| dependencies | unvetted-dep:@vates/xml | AI (dependencies): Same-org @vates scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:xo-collection | AI (dependencies): Same-org (vatesfr/xen-orchestra) package; stable false positive. | ai | |
| dependencies | unvetted-dep:@vates/xml-rpc | AI (dependencies): Same-org @vates scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:@vates/json-hash | AI (dependencies): Same-org @vates scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:@vates/obfuscate | AI (dependencies): Same-org @vates scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:pw | AI (dependencies): Small CLI password utility; stable dep in this package's ecosystem. | ai | |
| dependencies | unvetted-dep:json-rpc-protocol | AI (dependencies): Standard JSON-RPC utility; legitimate use in API connector. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/log | AI (dependencies): Same-org @xen-orchestra scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:@vates/coalesce-calls | AI (dependencies): Same-org @vates scoped package; stable false positive. | ai | |
| dependencies | unvetted-dep:bind-property-descriptor | AI (dependencies): Small utility; stable dep in this package's ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of Sigstore provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:http-request-plus | AI (dependencies): Known utility package used across xen-orchestra ecosystem. | ai | |
| dependencies | unvetted-dep:blocked | AI (dependencies): Event-loop monitoring utility; legitimate use in a Xen API connector. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 4.8.0 | 24 / 12 | |
| 4.7.8 | 24 / 12 | |
| 4.7.7 | 24 / 12 | |
| 4.7.6 | 24 / 12 | |
| 4.7.5 | 24 / 12 | |
| 4.7.4 | 24 / 12 | |
| 4.7.3 | 24 / 12 | |
| 4.7.2 | 24 / 12 | |
| 4.7.1 | 23 / 12 | |
| 4.7.0 | 23 / 12 | |
| 4.6.0 | 23 / 12 | |
| 4.5.0 | 24 / 12 | |
| 4.4.0 | 24 / 12 | |
| 4.3.2 | 24 / 12 | |
| 4.3.1 | 24 / 12 | |
| 4.3.0 | 25 / 12 | |
| 4.2.1 | 24 / 12 | |
| 4.2.0 | 23 / 12 | |
| 4.1.0 | 22 / 12 | |
| 4.0.0 | 22 / 12 |
v4.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mathieura) than the most recent previously approved version (b-nollet) on 2026-07-27, but mathieura 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.
v4.7.1
2 findingsThis version was published by a different npm account than previous versions on 2025-02-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
2 findingsThis version was published by a different npm account than previous versions on 2024-12-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
2 findingsThis version was published by a different npm account than previous versions on 2024-09-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
2 findingsThis version was published by a different npm account than previous versions on 2024-09-30. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-09-27. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
2 findingsThis version was published by a different npm account than previous versions on 2024-09-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findings[Accepted risk] Package 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.
v4.1.0
2 findings[Accepted risk] Package 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-24, 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.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.