@medusajs/file-s3
S3 protocol file storage for Medusa. Supports any S3-compatible storage provider
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): olijuhl is a known Medusa org maintainer; addition is consistent with org-level account management. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Paired with addition of another Medusa org account; consistent with internal rotation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @aws-sdk/lib-storage is a canonical AWS SDK package; expected addition for S3 multipart upload support. | ai | |
| dependencies | unvetted-peer-dep:@medusajs/framework | AI (dependencies): First-party peer dep from the same Medusa monorepo; stable pattern across all versions. | ai | |
| provenance | missing-githead | AI (provenance): Large monorepo package; gitHead absence may reflect CI publish environment change, not tampering. Content matches official repo. | ai | |
| provenance | publisher-changed | AI (provenance): Medusa migrated to GitHub Actions CI publishing with SLSA attestation; this is the expected new publisher for all future versions. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 4 / 1 | |
| 2.17.0 | 4 / 1 | |
| 2.16.0 | 4 / 1 | |
| 2.15.5 | 4 / 1 | |
| 2.15.3 | 4 / 1 | |
| 2.15.2 | 4 / 1 | |
| 2.15.1 | 4 / 1 | |
| 2.15.0 | 4 / 1 | |
| 2.14.2 | 4 / 1 | |
| 2.14.1 | 4 / 1 | |
| 2.14.0 | 4 / 1 | |
| 2.13.6 | 4 / 1 | |
| 2.13.5 | 4 / 1 | |
| 2.13.4 | 4 / 1 | |
| 2.13.3 | 4 / 1 | |
| 2.13.2 | 4 / 1 | |
| 2.13.1 | 4 / 1 | |
| 2.13.0 | 4 / 1 | |
| 2.12.6 | 4 / 1 | |
| 2.12.5 | 4 / 1 | |
| 2.12.4 | 4 / 1 | |
| 2.12.3 | 4 / 1 | |
| 2.12.2 | 3 / 1 | |
| 2.12.1 | 3 / 1 | |
| 2.12.0 | 3 / 1 | |
| 2.11.3 | 3 / 1 | |
| 2.11.2 | 3 / 7 | |
| 2.11.1 | 3 / 7 | |
| 2.11.0 | 3 / 7 | |
| 2.10.3 | 3 / 7 | |
| 2.10.2 | 3 / 7 | |
| 2.10.1 | 3 / 7 | |
| 2.10.0 | 3 / 7 | |
| 2.9.0 | 3 / 7 | |
| 2.8.8 | 3 / 7 | |
| 2.8.7 | 3 / 7 | |
| 2.8.6 | 3 / 7 | |
| 2.8.5 | 3 / 7 | |
| 2.8.4 | 3 / 7 | |
| 2.8.3 | 3 / 7 | |
| 2.8.2 | 3 / 7 | |
| 2.8.1 | 3 / 7 | |
| 2.8.0 | 3 / 7 | |
| 2.7.1 | 3 / 7 | |
| 2.7.0 | 3 / 7 | |
| 2.6.1 | 3 / 7 | |
| 2.6.0 | 3 / 7 | |
| 2.5.1 | 3 / 7 | |
| 2.5.0 | 3 / 7 | |
| 2.4.0 | 3 / 7 | |
| 2.3.1 | 3 / 7 | |
| 2.3.0 | 3 / 7 | |
| 2.2.0 | 3 / 7 | |
| 2.1.3 | 3 / 7 | |
| 2.1.2 | 3 / 7 | |
| 2.1.1 | 3 / 7 | |
| 2.1.0 | 3 / 7 | |
| 2.0.7 | 3 / 7 | |
| 2.0.6 | 3 / 7 | |
| 2.0.5 | 3 / 7 | |
| 2.0.4 | 3 / 7 | |
| 2.0.3 | 3 / 7 | |
| 2.0.2 | 3 / 7 | |
| 2.0.1 | 3 / 7 | |
| 2.0.0 | 3 / 7 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.