@medusajs/admin-bundler
Bundler for the Medusa admin dashboard.
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): Medusa monorepo migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): owjuhl removal paired with olijuhl addition; consistent with internal org maintainer rotation, not a hostile takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): olijuhl is an established publisher (611 approved) within the MedusaJS org; transition appears legitimate. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal MedusaJS monorepo package; sparse README and no keywords are expected for internal tooling. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): glob is a declared runtime dep used in config/build tooling; not a phantom dependency concern for this package. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a declared runtime dep used via config files; stable false positive for this bundler package. | ai | |
| phantom-deps | phantom-dep:autoprefixer | AI (phantom-deps): autoprefixer is a declared runtime dep used via config files; stable false positive for this bundler package. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 13 / 1 | |
| 2.16.0 | 13 / 1 | |
| 2.15.5 | 13 / 1 | |
| 2.15.3 | 13 / 1 | |
| 2.15.2 | 13 / 1 | |
| 2.15.1 | 13 / 1 | |
| 2.15.0 | 13 / 1 | |
| 2.14.2 | 13 / 1 | |
| 2.14.0 | 13 / 1 | |
| 2.13.6 | 13 / 1 | |
| 2.13.5 | 13 / 1 | |
| 2.13.4 | 13 / 1 | |
| 2.13.3 | 13 / 1 | |
| 2.13.2 | 13 / 1 | |
| 2.13.1 | 13 / 1 | |
| 2.13.0 | 13 / 1 | |
| 2.12.6 | 13 / 1 | |
| 2.12.5 | 13 / 1 | |
| 2.12.4 | 13 / 1 | |
| 2.12.3 | 13 / 1 | |
| 2.12.2 | 13 / 1 | |
| 2.12.1 | 13 / 1 | |
| 2.12.0 | 13 / 1 | |
| 2.11.3 | 13 / 1 | |
| 2.11.2 | 13 / 5 | |
| 2.10.3 | 13 / 5 | |
| 2.10.1 | 13 / 5 | |
| 2.10.0 | 13 / 5 | |
| 2.9.0 | 13 / 5 | |
| 2.8.8 | 13 / 5 | |
| 2.8.7 | 13 / 5 | |
| 2.8.6 | 13 / 5 | |
| 2.8.5 | 13 / 5 | |
| 2.8.4 | 13 / 5 | |
| 2.8.3 | 13 / 5 | |
| 2.8.2 | 13 / 5 | |
| 2.8.1 | 13 / 5 | |
| 2.8.0 | 13 / 5 | |
| 2.7.1 | 13 / 5 | |
| 2.7.0 | 13 / 5 | |
| 2.6.1 | 13 / 6 | |
| 2.6.0 | 13 / 6 | |
| 2.5.1 | 13 / 6 | |
| 2.5.0 | 13 / 6 | |
| 2.4.0 | 11 / 6 | |
| 2.3.1 | 10 / 6 | |
| 2.3.0 | 10 / 6 | |
| 2.2.0 | 9 / 6 | |
| 2.1.3 | 9 / 6 | |
| 2.1.2 | 9 / 6 | |
| 2.1.1 | 9 / 6 |
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 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.