← Home

@medusajs/locking

npm Repository Homepage

Locking Module for Medusa

66
Versions
MIT
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

sebrindomoliverjuhlnicolas-gorgasradevskiolijuhl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established Medusa monorepo package; missing gitHead reflects publish-env change, not malicious. ai
provenance no-provenance AI (provenance): Lack of Sigstore provenance is not a risk on its own for this trusted publisher. ai
maintainer-change maintainer-added AI (maintainer-change): Legitimate Medusa org contributor; monorepo maintainer churn is normal. ai
provenance publisher-changed AI (provenance): Medusa monorepo publishes via GitHub Actions CI/CD; transition from human publisher to automation is expected and backed by SLSA attestation. ai

Versions (showing 66 of 66)

Version Deps Published
2.18.0 0 / 2
2.17.1 0 / 2
2.17.0 0 / 2
2.16.0 0 / 2
2.15.5 0 / 2
2.15.3 0 / 2
2.15.2 0 / 2
2.15.1 0 / 2
2.15.0 0 / 2
2.14.2 0 / 2
2.14.1 0 / 2
2.14.0 0 / 2
2.13.6 0 / 2
2.13.5 0 / 2
2.13.4 0 / 2
2.13.3 0 / 2
2.13.2 0 / 2
2.13.1 0 / 2
2.13.0 0 / 2
2.12.6 0 / 2
2.12.5 0 / 2
2.12.4 0 / 2
2.12.3 0 / 2
2.12.2 0 / 2
2.12.1 0 / 2
2.12.0 0 / 2
2.11.3 0 / 2
2.11.2 0 / 8
2.11.1 0 / 8
2.11.0 0 / 8
2.10.3 0 / 12
2.10.2 0 / 12
2.10.1 0 / 12
2.10.0 0 / 12
2.9.0 0 / 12
2.8.8 0 / 12
2.8.7 0 / 12
2.8.6 0 / 12
2.8.5 0 / 12
2.8.4 0 / 12
2.8.3 0 / 12
2.8.2 0 / 12
2.8.1 0 / 12
2.8.0 0 / 12
2.7.1 0 / 12
2.7.0 0 / 12
2.6.1 0 / 12
2.6.0 0 / 12
2.5.1 0 / 12
2.5.0 0 / 12
2.4.0 0 / 12
2.3.1 0 / 12
2.3.0 0 / 12
2.2.0 0 / 12
2.1.3 0 / 12
2.1.2 0 / 12
2.1.1 0 / 12
2.1.0 0 / 12
2.0.7 0 / 12
2.0.6 0 / 12
2.0.5 0 / 12
2.0.4 0 / 12
2.0.3 0 / 12
2.0.2 0 / 12
2.0.1 0 / 12
2.0.0 0 / 12

v2.18.0

1 finding
HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.

v2.11.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.11.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.3

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.2

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.10.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: owjuhl.

LOW No provenance attestation provenance

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

v2.7.1

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.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: oliverjuhl → owjuhl (on 2025-03-10, known maintainer) provenance

This version was published by a different npm account (owjuhl) than the most recent previously approved version (oliverjuhl) on 2025-03-10, but owjuhl 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.

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.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.

v2.5.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.

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

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

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