@medusajs/workflows-sdk
Set of workflows tooling 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing, confirmed by SLSA provenance attestation. | ai | |
| provenance | no-provenance | AI (provenance): Medusa packages consistently lack provenance attestation; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:@medusajs/deps | AI (phantom-deps): @medusajs/deps is a same-org sibling dep declared in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 5 / 1 | |
| 2.16.0 | 5 / 1 | |
| 2.15.5 | 5 / 1 | |
| 2.15.3 | 5 / 1 | |
| 2.15.2 | 5 / 1 | |
| 2.15.1 | 5 / 1 | |
| 2.15.0 | 5 / 1 | |
| 2.14.2 | 5 / 1 | |
| 2.14.1 | 5 / 1 | |
| 2.14.0 | 5 / 1 | |
| 2.13.6 | 5 / 1 | |
| 2.13.5 | 5 / 1 | |
| 2.13.4 | 5 / 1 | |
| 2.13.3 | 5 / 1 | |
| 2.13.2 | 5 / 1 | |
| 2.13.1 | 5 / 1 | |
| 2.13.0 | 5 / 1 | |
| 2.12.6 | 5 / 1 | |
| 2.12.5 | 5 / 1 | |
| 2.12.4 | 5 / 1 | |
| 2.12.3 | 5 / 1 | |
| 2.12.2 | 5 / 1 | |
| 2.12.1 | 5 / 1 | |
| 2.12.0 | 5 / 1 | |
| 2.11.3 | 5 / 1 | |
| 2.11.2 | 5 / 8 | |
| 2.11.1 | 5 / 8 | |
| 2.11.0 | 5 / 8 | |
| 2.10.3 | 5 / 13 | |
| 2.10.2 | 5 / 13 | |
| 2.10.1 | 5 / 13 | |
| 2.10.0 | 5 / 13 | |
| 2.9.0 | 5 / 13 | |
| 2.8.8 | 5 / 13 | |
| 2.8.7 | 5 / 13 | |
| 2.8.6 | 5 / 13 | |
| 2.8.5 | 5 / 13 | |
| 2.8.4 | 5 / 13 | |
| 2.8.3 | 5 / 13 | |
| 2.8.2 | 5 / 13 | |
| 2.8.1 | 5 / 13 | |
| 2.8.0 | 5 / 13 | |
| 2.7.1 | 5 / 13 | |
| 2.7.0 | 5 / 13 | |
| 2.6.1 | 5 / 11 | |
| 2.6.0 | 5 / 11 | |
| 2.5.1 | 5 / 11 | |
| 2.5.0 | 5 / 11 | |
| 2.4.0 | 5 / 11 | |
| 2.3.1 | 5 / 11 | |
| 2.3.0 | 5 / 11 |
v2.18.0
2 findingsThis 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.
This version was published by a different npm account (olijuhl) than the most recent previously approved version (GitHub Actions) on 2026-07-23, 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.
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.