← Home

@medusajs/mcloud

npm Repository Homepage

Medusa Cloud CLI

4
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

Keywords

oclif

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@repo/build-detector AI (dependencies): Internal monorepo workspace:* dep in medusajs scoped package; expected. ai
phantom-deps phantom-dep:@oclif/plugin-help AI (phantom-deps): oclif plugin loaded via config, not direct import. ai
phantom-deps phantom-dep:@oclif/plugin-autocomplete AI (phantom-deps): oclif plugin loaded via config, not direct import. ai
phantom-deps phantom-dep:@repo/build-detector AI (phantom-deps): internal workspace build-time dep, bundled not imported at runtime. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.9 10 / 8
0.1.5 10 / 8
0.1.1 9 / 8
0.1.0 9 / 8

v0.1.9

2 findings
HIGH Publisher changed: olijuhl → GitHub Actions (on 2026-07-10) provenance

This version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.5

2 findings
HIGH Publisher changed: olijuhl → nicolas-gorga (on 2026-07-10) provenance

This version was published by a different npm account than previous versions on 2026-07-10. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.1.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.

v0.1.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.