← Home

@xwiki/platform-model-remote-url-api

npm Repository Homepage
7
Versions
LGPL 2.1
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

xwikiorgnpmtmortagneesurlimanuelleducpierre.jeanjeanmarius.dumitru.floreavmassolmichael.hamann

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): XWiki org package; publisher rotation among known community members is expected across versions. ai
maintainer-change maintainer-added AI (maintainer-change): vmassol is a known XWiki contributor; org-level maintainer additions are routine for this package. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across XWiki platform packages; not a malware indicator here. ai

Versions (showing 7 of 7)

Version Deps Published
18.4.0 2 / 12
18.3.0 2 / 12
18.2.1 2 / 10
18.2.0 2 / 10
18.1.0 2 / 8
18.0.1 2 / 8
18.0.0 2 / 8

v18.4.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: manuelleduc → surli (on 2026-05-27, known maintainer) provenance

This version was published by a different npm account (surli) than the most recent previously approved version (manuelleduc) on 2026-05-27, but surli 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.

v18.2.1

2 findings
HIGH Publisher changed: manuelleduc → michael.hamann (on 2026-04-09) provenance

This version was published by a different npm account than previous versions on 2026-04-09. 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.

v18.2.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.

v18.1.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: tmortagnee → michael.hamann (on 2026-02-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.

v18.0.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: marius.dumitru.florea → tmortagnee (on 2026-02-04) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.

v18.0.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.