@xen-orchestra/fs
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:qs | AI (typosquat): Scoped package @xen-orchestra/fs; Levenshtein match to 'qs' is a false positive with no brand impersonation. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @xen-orchestra/fs; Levenshtein match to 'pg' is a false positive with no brand impersonation. | ai | |
| phantom-deps | phantom-dep:readable-stream | AI (phantom-deps): readable-stream is a declared runtime dep used transitively; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@vates/decorate-with | AI (phantom-deps): Part of the vates ecosystem; likely used via config/decorator pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/abort-controller | AI (phantom-deps): Framework-scoped AWS SDK package loaded by convention; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 4.9.0 | 23 / 11 | |
| 4.8.0 | 23 / 10 | |
| 4.6.7 | 23 / 10 | |
| 4.6.6 | 23 / 10 | |
| 4.6.5 | 23 / 10 | |
| 4.6.4 | 23 / 10 | |
| 4.6.3 | 23 / 10 | |
| 4.6.2 | 23 / 10 | |
| 4.6.1 | 23 / 10 | |
| 4.6.0 | 23 / 10 | |
| 4.5.1 | 22 / 10 |
v4.9.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-22, 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.
v4.8.0
2 findingsPackage name '@xen-orchestra/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.7
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-02-23, 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.
v4.6.6
2 findingsPackage name '@xen-orchestra/fs' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.5
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 (mathieura) than the most recent previously approved version (b-nollet) on 2025-12-10, 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.6.4
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 (pdonias) than the most recent previously approved version (b-nollet) on 2025-10-06, but pdonias 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.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.