← Home

@batoanng/mui-components

npm

[![npm version](https://img.shields.io/npm/v/@batoanng/mui-components)](https://www.npmjs.com/package/@batoanng/mui-components) [![install size](https://packagephobia.com/badge?p=@batoanng/mui-components)](https://packagephobia.com/result?p=@batoanng/mui-

19
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

batoanng

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@batoanng/tsconfig AI (phantom-deps): Same-org build config; stable pattern for this package. ai
phantom-deps phantom-dep:@batoanng/eslint-config AI (phantom-deps): Same-org build config; stable pattern for this package. ai
phantom-deps phantom-dep:@batoanng/prettier-config AI (phantom-deps): Same-org build config; stable pattern for this package. ai
phantom-deps phantom-dep:file-selector AI (phantom-deps): Runtime dependency for file upload components; stable across versions. ai
phantom-deps phantom-dep:date-fns AI (phantom-deps): Runtime dependency used by date picker components; stable across versions. ai
phantom-deps phantom-dep:@tabler/icons-react AI (phantom-deps): Runtime dependency for icon components; stable across versions. ai
phantom-deps phantom-dep:@batoanng/utils AI (phantom-deps): Scoped org dependency; stable across versions. ai
phantom-deps phantom-dep:entities AI (phantom-deps): Runtime dependency for HTML entity handling; stable across versions. ai
phantom-deps phantom-dep:react-use AI (phantom-deps): Runtime dependency for React hooks; stable across versions. ai

Versions (showing 19 of 19)

Version Deps Published
3.7.0 5 / 27
3.6.0 6 / 26
3.5.4 6 / 31
3.5.3 6 / 49
3.5.2 6 / 49
3.5.1 6 / 49
3.5.0 6 / 49
3.3.0 6 / 49
3.2.0 6 / 49
3.0.9 6 / 49
3.0.8 6 / 49
3.0.7 6 / 49
3.0.6 6 / 49
3.0.5 6 / 49
3.0.4 6 / 51
3.0.3 5 / 50
3.0.2 5 / 50
3.0.1 5 / 50
3.0.0 8 / 48

v3.7.0

1 finding
LOW No provenance attestation provenance

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

v3.6.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.

v3.5.4

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.

v3.5.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.

v3.5.2

1 finding
LOW No provenance attestation provenance

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

v3.5.1

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.3.0

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.0.9

1 finding
LOW No provenance attestation provenance

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

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

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.

v3.0.5

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.

v3.0.4

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.

v3.0.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.

v3.0.2

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.

v3.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.

v3.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.