← Home

@mxenabled/mxui

npm

Package containing MX theme and common controls for MUI

21
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

sskousenblueeagle500jrexdavisnathan.nashthechirinosinphomercialjsfowleswolzeyashlylamarrmxdevexperiencemwclemyjameson13craigtingeyashley.wrightjamesonmxshalyn.huetteramyjeppson.mxwilliam.bridegroommx.devcodingloganwesrisenmay-mxmx-sabarigiristephanie.stammhassyyy_mxjordanboudreau

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@mui/system AI (phantom-deps): Peer/config-only reference pattern consistent with this UI library; stable false positive. ai
phantom-deps phantom-dep:react-dom AI (phantom-deps): Declared as peer dep for consumer use; not directly imported in library source is expected. ai
phantom-deps phantom-dep:@emotion/react AI (phantom-deps): Peer/runtime dep for MUI theming; not directly imported in library source is expected. ai
phantom-deps phantom-dep:@emotion/styled AI (phantom-deps): Peer/runtime dep for MUI theming; not directly imported in library source is expected. ai
phantom-deps phantom-dep:@mui/x-data-grid-pro AI (phantom-deps): Declared as peer dep; component library pattern — not directly imported at top level is expected. ai

Versions (showing 21 of 21)

Version Deps Published
2.7.0 12 / 33
2.6.1 12 / 33
2.6.0 12 / 33
2.5.3 12 / 33
2.5.2 12 / 33
2.5.1 12 / 33
2.5.0 12 / 33
2.4.1 12 / 33
2.4.0 12 / 33
2.3.0 12 / 33
2.2.7 12 / 33
2.2.4 12 / 33
2.2.3 12 / 33
2.2.2 12 / 33
2.2.1 12 / 33
2.2.0 12 / 33
2.1.1 12 / 33
2.1.0 12 / 33
2.0.1 12 / 33
2.0.0 12 / 33
1.5.16 13 / 39

v2.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.5.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.