@medusajs/dashboard
This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Legitimate maintainer within official medusajs org; no compromise indicators. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large bundled dist output normal for this dashboard package. | ai | |
| dependencies | unvetted-dep:lodash.set | AI (dependencies): Widely-used lodash micro-package, benign lodash split replacement. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): qrcode is a well-established library; addition is consistent with 2FA feature development in a major dashboard release. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dismissable-layer | AI (phantom-deps): Same as react-dialog; Radix UI transitive usage pattern. Stable FP. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): qs is a declared dep used via config/build tooling in this monorepo dashboard package; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component README links to docs; not a link farm. Stable FP for @medusajs/* packages. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime dep; loaded by convention, not direct import. Stable FP. | ai | |
| phantom-deps | phantom-dep:i18next-http-backend | AI (phantom-deps): i18n backend loaded via config, not direct import. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-dialog | AI (phantom-deps): Radix UI deps used via re-exports/config in this UI package. Stable FP. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 39 / 8 | |
| 2.16.0 | 39 / 8 | |
| 2.15.5 | 40 / 8 | |
| 2.15.3 | 39 / 7 | |
| 2.15.2 | 39 / 7 | |
| 2.15.1 | 39 / 7 | |
| 2.14.2 | 39 / 7 | |
| 2.14.1 | 39 / 4 | |
| 2.14.0 | 39 / 4 | |
| 2.13.6 | 39 / 4 | |
| 2.13.5 | 39 / 4 | |
| 2.13.4 | 39 / 4 | |
| 2.13.3 | 39 / 4 | |
| 2.13.2 | 39 / 4 | |
| 2.13.1 | 39 / 4 | |
| 2.13.0 | 39 / 4 | |
| 2.12.6 | 39 / 4 | |
| 2.12.5 | 39 / 4 | |
| 2.12.2 | 39 / 4 | |
| 2.12.1 | 39 / 4 | |
| 2.11.3 | 40 / 4 | |
| 2.11.2 | 37 / 18 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. This could indicate a legitimate maintainer transition or an account compromise.
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 than previous versions on 2025-12-03. This could indicate a legitimate maintainer transition or an account compromise.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.