@xen-orchestra/mixins
Mixins shared between xo-proxy and xo-server
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): Known org monorepo maintainer rotation, track record clean. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for HTTP Basic Auth header parsing — standard, non-malicious pattern stable across versions. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.20.1 | 9 / 0 | |
| 0.20.0 | 9 / 0 | |
| 0.19.0 | 9 / 0 | |
| 0.18.0 | 9 / 0 | |
| 0.17.1 | 9 / 0 | |
| 0.17.0 | 9 / 0 | |
| 0.16.5 | 9 / 0 | |
| 0.16.4 | 9 / 0 | |
| 0.16.3 | 9 / 0 | |
| 0.16.2 | 9 / 0 | |
| 0.16.1 | 9 / 1 | |
| 0.16.0 | 9 / 1 | |
| 0.15.1 | 9 / 1 |
v0.16.3
2 findingsThis version was published by a different npm account than previous versions on 2025-02-21. 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.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.