← Home

@medusajs/user

npm Repository Homepage

Medusa Users module

64
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
bogus-package bogus-package AI (bogus-package): Internal monorepo module; sparse README and no keywords are expected for @medusajs scoped packages. ai
provenance publisher-changed AI (provenance): Medusajs migrated to GitHub Actions CI publishing with SLSA attestation; publisher change is expected and verifiable. ai

Versions (showing 64 of 64)

Version Deps Published
2.18.0 1 / 2
2.17.0 1 / 2
2.16.0 1 / 2
2.15.5 1 / 2
2.15.3 1 / 2
2.15.2 1 / 2
2.15.1 1 / 2
2.15.0 1 / 2
2.14.2 1 / 2
2.14.1 1 / 2
2.14.0 1 / 2
2.13.6 1 / 2
2.13.5 1 / 2
2.13.4 1 / 2
2.13.3 1 / 2
2.13.2 1 / 2
2.13.1 1 / 2
2.13.0 1 / 2
2.12.6 1 / 2
2.12.5 1 / 2
2.12.4 1 / 2
2.12.3 1 / 2
2.12.2 1 / 2
2.12.1 1 / 2
2.12.0 1 / 2
2.11.3 1 / 2
2.11.2 1 / 8
2.11.1 1 / 8
2.11.0 1 / 8
2.10.3 1 / 12
2.10.2 1 / 12
2.10.1 1 / 12
2.10.0 1 / 12
2.8.8 1 / 12
2.8.7 1 / 12
2.8.6 1 / 12
2.8.5 1 / 12
2.8.4 1 / 12
2.8.3 1 / 12
2.8.2 1 / 12
2.8.1 1 / 12
2.8.0 1 / 12
2.7.1 1 / 12
2.7.0 1 / 12
2.6.1 1 / 12
2.6.0 1 / 12
2.5.1 1 / 12
2.5.0 1 / 12
2.4.0 1 / 12
2.3.1 1 / 12
2.3.0 1 / 12
2.2.0 1 / 12
2.1.3 1 / 12
2.1.2 1 / 12
2.1.1 1 / 12
2.1.0 1 / 12
2.0.7 1 / 12
2.0.6 1 / 12
2.0.5 1 / 12
2.0.4 1 / 12
2.0.3 1 / 12
2.0.2 1 / 12
2.0.1 1 / 12
2.0.0 1 / 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.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. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.0

1 finding
LOW No provenance attestation provenance

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

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.