@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, 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher has strong track record (125 approved, 0 rejected); consistent with monorepo maintainer rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same maintainer transition, corroborated by trusted publisher history. | 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 | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @xen-orchestra/fs; Levenshtein match to 'qs' is a false positive with no brand impersonation. | 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 | |
| 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 | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @xen-orchestra/fs; Levenshtein match to 'pg' is a false positive with no brand impersonation. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.9.2 | 23 / 11 | |
| 4.9.1 | 23 / 11 | |
| 4.9.0 | 23 / 11 | |
| 4.8.0 | 23 / 10 | |
| 4.7.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 | |
| 4.5.0 | 22 / 10 | |
| 4.4.1 | 22 / 10 | |
| 4.4.0 | 22 / 10 | |
| 4.3.0 | 22 / 10 | |
| 4.2.1 | 22 / 10 | |
| 4.2.0 | 22 / 11 | |
| 4.1.7 | 22 / 11 |
v4.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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 (pdonias) 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.
v4.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 (mathieura) than the most recent previously approved version (pdonias) 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.
v4.4.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 (pdonias) than the most recent previously approved version (b-nollet) on 2025-01-28, 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.3.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-25. 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.
v4.2.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 (pdonias) on 2024-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.
v4.2.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 (pdonias) on 2024-10-28, 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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.