@xen-orchestra/xapi
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:hapi | AI (typosquat): Scoped @xen-orchestra/xapi is a long-established Vates SAS monorepo package; no relation to hapi. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes a XAPI API response (VDI.list_changed_blocks) into a Buffer; legitimate protocol handling, not obfuscation. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 8.8.0 | 18 / 0 | |
| 8.7.2 | 18 / 0 | |
| 8.6.4 | 18 / 0 | |
| 8.6.1 | 18 / 0 | |
| 8.6.0 | 18 / 0 | |
| 8.5.0 | 18 / 0 | |
| 8.4.2 | 18 / 0 | |
| 8.4.1 | 18 / 0 | |
| 8.4.0 | 18 / 0 | |
| 8.3.3 | 18 / 0 | |
| 8.3.2 | 18 / 0 | |
| 8.3.1 | 18 / 0 | |
| 8.3.0 | 18 / 0 | |
| 8.2.0 | 17 / 0 |
v8.8.0
2 findingsPackage name '@xen-orchestra/xapi' is 1 edit(s) away from popular package 'hapi'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.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 (b-nollet) than the most recent previously approved version (mlssfrncjrg) on 2026-04-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.
v8.6.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.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 (mlssfrncjrg) than the most recent previously approved version (b-nollet) on 2025-11-24, but mlssfrncjrg 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.
v8.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.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 (pierre.brunet289) on 2025-10-30, 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.
v8.4.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 (b-nollet) than the most recent previously approved version (pierre.brunet289) on 2025-10-27, 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.
v8.4.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 (pierre.brunet289) on 2025-09-04, 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.
v8.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.