@medusajs/draft-order
A draft order plugin 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@uiw/react-json-view | AI (dependencies): Legit UI dependency in an official Medusa admin plugin; stable across versions. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Well-known utility deps consistent with Medusa monorepo dependency bumps. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with account rename within same org, provenance unchanged vs prior approved. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is part of the Medusa org; legitimate team package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): @babel/runtime is a transitive runtime dep commonly used by convention in compiled packages; stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 12 / 9 | |
| 2.17.1 | 12 / 9 | |
| 2.17.0 | 12 / 9 | |
| 2.15.5 | 12 / 8 | |
| 2.15.3 | 12 / 8 | |
| 2.15.2 | 12 / 8 | |
| 2.15.1 | 12 / 8 | |
| 2.15.0 | 12 / 8 | |
| 2.14.2 | 12 / 8 | |
| 2.14.1 | 12 / 8 | |
| 2.14.0 | 12 / 8 | |
| 2.13.6 | 12 / 8 | |
| 2.13.5 | 12 / 8 | |
| 2.13.4 | 12 / 8 | |
| 2.13.3 | 12 / 8 | |
| 2.13.2 | 12 / 8 | |
| 2.13.0 | 12 / 8 | |
| 2.12.6 | 12 / 8 | |
| 2.12.5 | 12 / 8 | |
| 2.12.4 | 12 / 8 | |
| 2.12.3 | 12 / 8 | |
| 2.12.2 | 12 / 8 | |
| 2.12.1 | 12 / 8 | |
| 2.12.0 | 12 / 8 | |
| 2.11.3 | 12 / 8 | |
| 2.11.2 | 9 / 22 | |
| 2.11.1 | 9 / 22 | |
| 2.11.0 | 9 / 22 | |
| 2.10.3 | 9 / 29 | |
| 2.10.2 | 9 / 29 | |
| 2.10.1 | 9 / 29 | |
| 2.10.0 | 9 / 29 |
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 unknown date, 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.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2026-01-22. It has since remained available on npm for 182 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.6
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2026-01-22. It has since remained available on npm for 182 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.5
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2026-01-09. It has since remained available on npm for 195 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.4
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2026-01-06. It has since remained available on npm for 197 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.3
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2025-12-17. It has since remained available on npm for 218 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.2
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2025-12-11. It has since remained available on npm for 224 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2025-12-03. It has since remained available on npm for 232 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
2 findingsThis version was published by a different npm account (olijuhl) than the most recent previously approved version (owjuhl) on 2025-12-01. It has since remained available on npm for 233 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.