← Home

@devx-commerce/strapi

npm

Medusa plugin for Strapi as CMS

8
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

brijeshagarwalvasuchapadiabrijesh_at_devxchirag12345

Keywords

medusa-v2medusapluginmedusa-pluginmedusa-plugin-cmsmedusa-plugin-integrationmedusa-plugin-strapistrapi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@strapi/client AI (dependencies): @strapi/client is the official Strapi JS client; expected runtime dep for a Medusa-Strapi integration plugin. ai
typosquat typosquat.levenshtein:stripe AI (typosquat): Package is a Medusa plugin for Strapi CMS; 'strapi' in the name refers to the CMS, not a misspelling of 'stripe'. ai

Versions (showing 8 of 8)

Version Deps Published
0.0.12 0 / 26
0.0.11 0 / 26
0.0.7 0 / 27
0.0.6 0 / 27
0.0.5 0 / 27
0.0.4 0 / 27
0.0.3 0 / 27
0.0.2 1 / 26

v0.0.12

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.0.11

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

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.0.3

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.0.2

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.