@xen-orchestra/rest-api
REST API to manage your XOA
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are from the same Vates org; consistent with the package's ecosystem and no malicious indicators. | ai | |
| phantom-deps | phantom-dep:@vates/types | AI (phantom-deps): Type-only dependency declared in config; not imported at runtime. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/log | AI (dependencies): First-party @xen-orchestra monorepo dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/xapi | AI (dependencies): First-party @xen-orchestra monorepo dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/backups | AI (dependencies): First-party @xen-orchestra monorepo dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@vates/task | AI (dependencies): First-party @vates monorepo dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:@vates/async-each | AI (dependencies): First-party @vates monorepo dependency; stable for this package. | ai | |
| dependencies | unvetted-dep:tsoa | AI (dependencies): Well-known TypeScript OpenAPI framework; no malware indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established Vates SAS monorepo package; no provenance is consistent across all versions. | ai | |
| dependencies | unvetted-dep:golike-defer | AI (dependencies): Known utility library; no malware indicators. | ai | |
| dependencies | unvetted-dep:value-matcher | AI (dependencies): Known utility library; no malware indicators. | ai | |
| dependencies | unvetted-dep:complex-matcher | AI (dependencies): Known utility library; no malware indicators. | ai | |
| dependencies | unvetted-dep:promise-toolbox | AI (dependencies): Known utility library; no malware indicators. | ai | |
| dependencies | unvetted-dep:xo-remote-parser | AI (dependencies): Vates SAS xo ecosystem package; stable for this package. | ai | |
| dependencies | unvetted-dep:inversify-binding-decorators | AI (dependencies): Known IoC decorator library; no malware indicators. | ai | |
| dependencies | unvetted-dep:xo-common | AI (dependencies): Vates SAS xo ecosystem package; stable for this package. | ai | |
| dependencies | unvetted-dep:@xen-orchestra/acl | AI (dependencies): First-party @xen-orchestra monorepo dependency; stable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.36.0 | 21 / 7 | |
| 0.32.0 | 21 / 7 | |
| 0.30.0 | 19 / 6 | |
| 0.11.0 | 16 / 6 | |
| 0.10.0 | 16 / 6 | |
| 0.9.0 | 14 / 6 | |
| 0.8.0 | 9 / 6 | |
| 0.6.0 | 9 / 6 | |
| 0.5.0 | 9 / 6 | |
| 0.4.0 | 9 / 6 | |
| 0.3.0 | 9 / 5 | |
| 0.2.0 | 9 / 5 | |
| 0.1.2 | 9 / 5 | |
| 0.1.1 | 9 / 5 | |
| 0.1.0 | 9 / 5 |
v0.36.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 (pierre.brunet289) 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.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.
v0.4.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 (mathieura) on 2025-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.
v0.3.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 (olivier.f) on 2025-03-31, 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.
v0.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 (mathieura) than the most recent previously approved version (olivier.f) on 2025-03-26, 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.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.