@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.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 | |
| 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 | |
| phantom-deps | phantom-dep:@radix-ui/react-dismissable-layer | AI (phantom-deps): Same as react-dialog; Radix UI transitive usage pattern. Stable FP. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component README links to docs; not a link farm. Stable FP for @medusajs/* packages. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 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 |
v2.15.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.