← Home

@xen-orchestra/backups

npm Repository Homepage

<!-- DO NOT EDIT MANUALLY, THIS FILE HAS BEEN GENERATED -->

64
Versions
AGPL-3.0-or-later
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

mpitonmlssfrncjrgmathieuraflorent.beauchampjulien-fmarsaudpdoniasbenjireistgoettelmannb-nolletjoris-kelise-folivier.fpierre.brunet289

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher has strong track record (54 approved, 0 rejected); consistent with team transition. ai
phantom-deps phantom-dep:xen-api AI (phantom-deps): xen-api is a declared dep used via config/indirect references in this monorepo package; stable false positive. ai
phantom-deps phantom-dep:@iarna/toml AI (phantom-deps): Config-file reference pattern in monorepo; stable false positive for this package. ai
phantom-deps phantom-dep:@vates/nbd-client AI (phantom-deps): Config-file reference pattern in monorepo; stable false positive for this package. ai
semgrep semgrep:hex-decode AI (semgrep): Hex literals are magic number constants for file format detection (gzip, zstd), not obfuscated payloads. ai

Versions (showing 64 of 64)

Version Deps Published
0.73.8 40 / 5
0.73.7 40 / 5
0.73.6 40 / 5
0.73.5 40 / 5
0.73.4 40 / 5
0.73.3 40 / 5
0.73.2 40 / 5
0.73.1 40 / 5
0.73.0 40 / 5
0.72.1 38 / 4
0.72.0 38 / 4
0.71.3 37 / 4
0.71.2 37 / 4
0.71.1 37 / 4
0.71.0 37 / 4
0.70.0 37 / 4
0.69.5 37 / 4
0.69.4 37 / 4
0.69.3 37 / 4
0.69.2 37 / 4
0.69.1 37 / 4
0.69.0 37 / 4
0.68.2 37 / 4
0.68.1 37 / 4
0.68.0 37 / 4
0.67.2 37 / 4
0.67.1 37 / 4
0.67.0 37 / 4
0.66.0 37 / 4
0.65.0 37 / 4
0.64.3 37 / 4
0.64.2 37 / 4
0.64.1 37 / 4
0.64.0 37 / 4
0.63.0 37 / 4
0.62.0 37 / 4
0.61.2 36 / 4
0.61.1 36 / 4
0.61.0 36 / 4
0.60.0 36 / 4
0.59.0 34 / 4
0.58.4 34 / 4
0.58.3 34 / 4
0.58.2 34 / 4
0.58.1 34 / 4
0.58.0 34 / 4
0.57.0 34 / 4
0.56.0 34 / 4
0.55.0 34 / 4
0.54.3 33 / 4
0.54.2 33 / 4
0.54.1 33 / 5
0.54.0 33 / 5
0.53.1 33 / 5
0.53.0 33 / 5
0.52.3 32 / 5
0.52.2 32 / 5
0.52.1 32 / 5
0.52.0 32 / 5
0.51.0 32 / 5
0.50.0 32 / 5
0.49.1 32 / 5
0.49.0 32 / 5
0.48.1 32 / 5

v0.73.8

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → mathieura (on 2026-07-27, known maintainer) provenance

This version was published by a different npm account (mathieura) than the most recent previously approved version (b-nollet) 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.73.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.73.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.73.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.73.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.59.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.4

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → mathieura (on 2025-03-26, known maintainer) provenance

This version was published by a different npm account (mathieura) than the most recent previously approved version (b-nollet) 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.58.3

2 findings
HIGH Publisher changed: b-nollet → olivier.f (on 2025-03-04) provenance

This version was published by a different npm account than previous versions on 2025-03-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.2

2 findings
HIGH Publisher changed: b-nollet → olivier.f (on 2025-02-21) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.58.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien-f → b-nollet (on 2025-01-30, known maintainer) provenance

This version was published by a different npm account (b-nollet) than the most recent previously approved version (julien-f) on 2025-01-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.

v0.58.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien-f → pdonias (on 2025-01-28, known maintainer) provenance

This version was published by a different npm account (pdonias) than the most recent previously approved version (julien-f) 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.

v0.57.0

2 findings
HIGH Publisher changed: julien-f → sebastianczech (on 2024-12-18) provenance

This version was published by a different npm account than previous versions on 2024-12-18. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.56.0

2 findings
HIGH Publisher changed: julien-f → sebastianczech (on 2024-12-16) provenance

This version was published by a different npm account than previous versions on 2024-12-16. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.55.0

2 findings
HIGH Publisher changed: julien-f → joris-k (on 2024-11-28) provenance

This version was published by a different npm account than previous versions on 2024-11-28. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.54.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → julien-f (on 2024-11-14, known maintainer) provenance

This version was published by a different npm account (julien-f) than the most recent previously approved version (b-nollet) on 2024-11-14, but julien-f 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.54.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.54.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien-f → b-nollet (on 2024-10-28, known maintainer) provenance

This version was published by a different npm account (b-nollet) than the most recent previously approved version (julien-f) 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.

v0.54.0

2 findings
HIGH Publisher changed: julien-f → stephane-m-dev (on 2024-09-27) provenance

This version was published by a different npm account than previous versions on 2024-09-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mathieura → julien-f (on 2024-09-10, known maintainer) provenance

This version was published by a different npm account (julien-f) than the most recent previously approved version (mathieura) on 2024-09-10, but julien-f 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.53.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.52.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → mathieura (on 2024-08-28, known maintainer) provenance

This version was published by a different npm account (mathieura) than the most recent previously approved version (b-nollet) on 2024-08-28, 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.52.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: julien-f → b-nollet (on 2024-07-25, known maintainer) provenance

This version was published by a different npm account (b-nollet) than the most recent previously approved version (julien-f) on 2024-07-25, 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.52.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mathieura → julien-f (on 2024-07-05, known maintainer) provenance

This version was published by a different npm account (julien-f) than the most recent previously approved version (mathieura) on 2024-07-05, but julien-f 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.52.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.51.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.50.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: pdonias → mathieura (on 2024-06-27, known maintainer) provenance

This version was published by a different npm account (mathieura) than the most recent previously approved version (pdonias) on 2024-06-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.49.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → pdonias (on 2024-05-31, known maintainer) provenance

This version was published by a different npm account (pdonias) than the most recent previously approved version (b-nollet) on 2024-05-31, 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.

v0.49.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: b-nollet → mlssfrncjrg (on 2024-05-30, known maintainer) provenance

This version was published by a different npm account (mlssfrncjrg) than the most recent previously approved version (b-nollet) on 2024-05-30, but mlssfrncjrg 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.48.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.