@xen-orchestra/web-core
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vueuse/shared | AI (phantom-deps): Peer/transitive usage pattern in Vue ecosystem; stable false positive. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-solid-svg-icons | AI (phantom-deps): Icon set loaded via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/free-regular-svg-icons | AI (phantom-deps): Icon set loaded via config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@regle/schemas | AI (phantom-deps): Config-file-only reference pattern consistent with other accepted phantom deps in this package. | ai | |
| phantom-deps | phantom-dep:vue-virtual-scroller | AI (phantom-deps): Config-referenced dep; stable false positive for this Vue UI library. | ai | |
| phantom-deps | phantom-dep:echarts | AI (phantom-deps): Font/chart deps loaded by convention in Vue build tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fortawesome/vue-fontawesome | AI (phantom-deps): Config-referenced Vue plugin; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/d3-time-format | AI (phantom-deps): Type-only package loaded by framework convention; stable false positive. | ai | |
| phantom-deps | phantom-dep:@novnc/novnc | AI (phantom-deps): Referenced in config/type declarations; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:iterable-backoff | AI (phantom-deps): Config-referenced dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fontsource/poppins | AI (phantom-deps): Font package loaded by convention; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.54.0 | 26 / 7 | |
| 0.51.0 | 23 / 7 | |
| 0.50.0 | 23 / 7 | |
| 0.49.0 | 23 / 7 | |
| 0.47.0 | 23 / 7 | |
| 0.45.0 | 23 / 7 | |
| 0.42.0 | 21 / 7 | |
| 0.39.1 | 21 / 7 | |
| 0.39.0 | 21 / 7 | |
| 0.34.0 | 21 / 7 | |
| 0.31.0 | 20 / 7 | |
| 0.24.0 | 19 / 7 | |
| 0.20.1 | 18 / 7 | |
| 0.20.0 | 18 / 7 |
v0.54.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 (pierre.brunet289) than the most recent previously approved version (b-nollet) on 2026-05-28, but pierre.brunet289 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.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.