@medusajs/file-local
Local filesystem file storage for Medusa
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Medusa packages historically published without Sigstore provenance; stable pattern for this package family. | ai | |
| provenance | publisher-changed | AI (provenance): Medusa monorepo migrated to GitHub Actions CI publishing with SLSA provenance; this is the expected new publisher pattern. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 0 / 1 | |
| 2.17.0 | 0 / 1 | |
| 2.16.0 | 0 / 1 | |
| 2.15.5 | 0 / 1 | |
| 2.15.3 | 0 / 1 | |
| 2.15.2 | 0 / 1 | |
| 2.15.1 | 0 / 1 | |
| 2.15.0 | 0 / 1 | |
| 2.14.2 | 0 / 1 | |
| 2.14.1 | 0 / 1 | |
| 2.14.0 | 0 / 1 | |
| 2.13.6 | 0 / 1 | |
| 2.13.5 | 0 / 1 | |
| 2.13.4 | 0 / 1 | |
| 2.13.3 | 0 / 1 | |
| 2.13.2 | 0 / 1 | |
| 2.13.1 | 0 / 1 | |
| 2.13.0 | 0 / 1 | |
| 2.12.6 | 0 / 1 | |
| 2.12.5 | 0 / 1 | |
| 2.12.4 | 0 / 1 | |
| 2.12.3 | 0 / 1 | |
| 2.12.2 | 0 / 1 | |
| 2.12.1 | 0 / 1 | |
| 2.12.0 | 0 / 1 | |
| 2.11.3 | 0 / 1 | |
| 2.11.2 | 0 / 6 | |
| 2.11.1 | 0 / 6 | |
| 2.11.0 | 0 / 6 | |
| 2.10.3 | 0 / 6 | |
| 2.10.2 | 0 / 6 | |
| 2.10.1 | 0 / 6 | |
| 2.10.0 | 0 / 6 | |
| 2.9.0 | 0 / 6 | |
| 2.8.8 | 0 / 6 | |
| 2.8.7 | 0 / 6 | |
| 2.8.6 | 0 / 6 | |
| 2.8.5 | 0 / 6 | |
| 2.8.4 | 0 / 6 | |
| 2.8.3 | 0 / 6 | |
| 2.8.2 | 0 / 6 | |
| 2.8.1 | 0 / 6 | |
| 2.8.0 | 0 / 6 | |
| 2.7.1 | 0 / 6 | |
| 2.7.0 | 0 / 6 | |
| 2.6.1 | 0 / 6 | |
| 2.6.0 | 0 / 6 | |
| 2.5.1 | 0 / 6 | |
| 2.5.0 | 0 / 6 | |
| 2.4.0 | 0 / 6 | |
| 2.3.1 | 0 / 6 | |
| 2.3.0 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.3 | 0 / 6 | |
| 2.1.2 | 0 / 6 | |
| 2.1.1 | 0 / 6 | |
| 2.1.0 | 0 / 6 | |
| 2.0.7 | 0 / 6 | |
| 2.0.6 | 0 / 6 | |
| 2.0.5 | 0 / 6 | |
| 2.0.4 | 0 / 6 | |
| 2.0.3 | 0 / 6 | |
| 2.0.2 | 0 / 6 | |
| 2.0.1 | 0 / 6 | |
| 2.0.0 | 0 / 6 |
v2.18.0
1 findingThis 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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] 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[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.