@xen-orchestra/backups AGPL-3.0-or-later 34 versions

@xen-orchestra/backups

npm Repository Homepage

34

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/05/29
phantom-deps	phantom-dep:@iarna/toml	AI (phantom-deps): Config-file reference pattern in monorepo; stable false positive for this package.	ai	2026/05/29
phantom-deps	phantom-dep:@vates/nbd-client	AI (phantom-deps): Config-file reference pattern in monorepo; stable false positive for this package.	ai	2026/05/29
semgrep	semgrep:hex-decode	AI (semgrep): Hex literals are magic number constants for file format detection (gzip, zstd), not obfuscated payloads.	ai	2026/05/27

Versions (showing 34 of 34)

Version	Deps	Published
0.73.2	40 / 5	2026-06-01
0.73.1	40 / 5	2026-05-22
0.73.0	40 / 5	2026-05-22
0.72.1	38 / 4	2026-04-29
0.72.0	38 / 4	2026-04-24
0.71.3	37 / 4	2026-04-14
0.71.2	37 / 4	2026-04-03
0.71.1	37 / 4	2026-04-01
0.71.0	37 / 4	2026-03-31
0.70.0	37 / 4	2026-03-27
0.69.5	37 / 4	2026-04-20
0.69.4	37 / 4	2026-03-09
0.69.3	37 / 4	2026-03-06
0.69.2	37 / 4	2026-02-27
0.69.1	37 / 4	2026-02-25
0.69.0	37 / 4	2026-02-23
0.68.2	37 / 4	2026-02-09
0.68.1	37 / 4	2026-02-05
0.68.0	37 / 4	2026-01-23
0.67.2	37 / 4	2026-01-06
0.67.1	37 / 4	2025-12-10
0.67.0	37 / 4	2025-11-24
0.66.0	37 / 4	2025-10-30
0.65.0	37 / 4	2025-10-27
0.64.3	37 / 4	2025-09-25
0.64.2	37 / 4	2025-09-04
0.64.1	37 / 4	2025-08-28
0.64.0	37 / 4	2025-08-27
0.63.0	37 / 4	2025-07-28
0.62.0	37 / 4	2025-06-27
0.61.2	36 / 4	2025-06-23
0.61.1	36 / 4	2025-06-05
0.61.0	36 / 4	2025-05-27
0.60.0	36 / 4	2025-05-23

v0.73.2

1 finding

LOW No provenance attestation provenance

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

v0.73.1

1 finding

LOW No provenance attestation provenance

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

v0.73.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 → pierre.brunet289 (on 2026-05-22, known maintainer) provenance

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.

v0.72.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.

v0.72.0

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.

v0.71.3

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.

v0.71.2

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.

v0.71.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.

v0.71.0

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.

v0.70.0

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.

v0.69.5

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.

v0.69.4

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.

v0.69.3

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.

v0.69.2

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.

v0.69.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.

v0.69.0

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.

v0.68.2

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.

v0.68.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.

v0.68.0

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.

v0.67.2

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.

v0.67.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.

v0.67.0

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.

v0.66.0

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.

v0.65.0

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.

v0.64.3

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.

v0.64.2

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.

v0.64.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.

v0.64.0

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.

v0.63.0

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.

v0.62.0

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.

v0.61.2

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.

v0.61.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.

v0.61.0

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.

v0.60.0

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.