@material-ui/types — Greenflagged

Material-UI Types - Utility types for Material-UI.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

oliviertassinarihai-ceambrookesjoshwoodingeps1lonmnajdovasiriwatknpmichaldudak

Keywords

reactreact-componentmaterial-uitypes

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transition between MUI core maintainers (eps1lon → oliviertassinari). Both are well-known contributors to the MUI project.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
6.0.2	0 / 0	2021-08-09
6.0.1	0 / 0	2021-05-31
6.0.0	0 / 0	2021-04-27
5.1.8	0 / 0	2021-04-20
5.1.7	0 / 0	2021-02-11
5.1.6	0 / 0	2021-01-26
5.1.5	0 / 0	2021-01-14
5.1.4	0 / 0	2021-01-04
5.1.3	0 / 0	2020-12-30
5.1.2	0 / 0	2020-12-21
5.1.1	0 / 0	2020-12-13
5.1.0	0 / 0	2020-05-11
5.0.1	0 / 0	2020-04-11
5.0.0	0 / 0	2020-01-22
4.1.1	1 / 0	2019-06-23
4.1.0	0 / 0	2019-06-10
4.0.1	0 / 0	2019-05-27
4.0.0	0 / 0	2019-05-23

v6.0.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oliviertassinari → siriwatknp (on 2021-08-09) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-08-09. This could indicate a legitimate maintainer transition or an account compromise.

v6.0.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mnajdova → oliviertassinari (on 2021-05-31) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-05-31. This could indicate a legitimate maintainer transition or an account compromise.

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.1.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oliviertassinari → mnajdova (on 2021-04-20) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-04-20. This could indicate a legitimate maintainer transition or an account compromise.

v5.1.7

2 findings

HIGH Publisher changed: eps1lon → oliviertassinari (on 2021-02-11) provenance

This version was published by a different npm account than previous versions on 2021-02-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.1.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mnajdova → eps1lon (on 2021-01-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-01-26. This could indicate a legitimate maintainer transition or an account compromise.

v5.1.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oliviertassinari → mnajdova (on 2021-01-14) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2021-01-14. This could indicate a legitimate maintainer transition or an account compromise.

v5.1.4

2 findings

HIGH Publisher changed: mnajdova → oliviertassinari (on 2021-01-04) provenance

This version was published by a different npm account than previous versions on 2021-01-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v5.1.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: oliviertassinari → mnajdova (on 2020-12-30) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2020-12-30. This could indicate a legitimate maintainer transition or an account compromise.

v5.1.2

1 finding

LOW No provenance attestation provenance

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

v5.1.1

1 finding

LOW No provenance attestation provenance

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

v5.0.1

1 finding

LOW No provenance attestation provenance

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

v5.0.0

1 finding

LOW No provenance attestation provenance

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

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

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