← Home

@medusajs/analytics

npm Repository Homepage

Medusa Analytics module

39
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 no-provenance AI (provenance): Large established monorepo; provenance not historically enabled for this package. ai
bogus-package bogus-package AI (bogus-package): Medusa monorepo module; sparse README and no keywords are expected for internal framework packages. ai
provenance publisher-changed AI (provenance): Medusajs migrated to GitHub Actions CI/CD publishing with SLSA provenance; publisher change is expected and verified. ai

Versions (showing 39 of 39)

Version Deps Published
2.18.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.2 0 / 8
2.10.1 0 / 8
2.10.0 0 / 8
2.9.0 0 / 8
2.8.8 0 / 8
2.8.7 0 / 8
2.8.6 0 / 8
2.8.5 0 / 8
2.8.4 0 / 8
2.8.3 0 / 8
2.8.2 0 / 8

v2.18.0

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

INFO Publisher changed: GitHub Actions → olijuhl (on unknown date, known maintainer) provenance

This version was published by a different npm account (olijuhl) than the most recent previously approved version (GitHub Actions) on unknown date, but olijuhl 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.