material-ui-popup-state
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): Likely used in compiled/bundled output not scanned as source text. | ai | |
| npm-metadata | url-dep:flow-copy-source | AI (npm-metadata): Dev-only dep pointing to maintainer's own fork; not a runtime risk. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.3.7 | 4 / 0 | |
| 5.3.6 | 4 / 0 | |
| 5.3.5 | 4 / 0 | |
| 5.3.4 | 4 / 0 | |
| 5.3.3 | 4 / 0 | |
| 5.3.2 | 5 / 0 | |
| 5.3.1 | 5 / 0 | |
| 5.3.0 | 5 / 0 | |
| 5.2.1 | 5 / 0 | |
| 5.2.0 | 5 / 0 | |
| 5.1.3 | 5 / 0 | |
| 5.1.2 | 5 / 0 | |
| 5.1.1 | 5 / 0 | |
| 5.1.0 | 5 / 0 | |
| 5.0.11 | 5 / 0 | |
| 5.0.10 | 4 / 67 | |
| 5.0.9 | 4 / 67 | |
| 5.0.8 | 4 / 67 | |
| 5.0.7 | 4 / 67 | |
| 5.0.6 | 4 / 67 | |
| 5.0.5 | 4 / 67 | |
| 5.0.4 | 4 / 67 | |
| 5.0.3 | 4 / 67 | |
| 5.0.2 | 4 / 67 | |
| 5.0.1 | 4 / 67 | |
| 5.0.0 | 4 / 67 |
v5.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.