@material-ui/pickers
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): mnajdova is a known MUI-org maintainer, not a suspicious new account. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal team turnover on long-lived MUI project, no takeover evidence. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Legacy package with slow release cadence; no material code changes accompany this publish. | ai | |
| source-diff | net-exec-file-transition:dist/material-ui-pickers.umd.min.js | AI (source-diff): UMD bundle module wiring; false positive on minified rollup output for this package. | ai | |
| phantom-deps | phantom-dep:@types/styled-jsx | AI (phantom-deps): Type-only package loaded by convention; phantom-dep false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 3.3.11 | 6 / 0 | |
| 3.3.10 | 6 / 0 | |
| 3.2.10 | 6 / 0 | |
| 3.2.9 | 6 / 0 | |
| 3.2.8 | 5 / 0 | |
| 3.2.7 | 5 / 0 | |
| 3.2.6 | 5 / 0 | |
| 3.2.5 | 6 / 0 | |
| 3.2.4 | 6 / 0 | |
| 3.2.3 | 6 / 0 | |
| 3.2.2 | 6 / 0 | |
| 3.2.1 | 6 / 0 | |
| 3.2.0 | 5 / 0 | |
| 3.1.2 | 5 / 0 | |
| 3.1.1 | 5 / 0 | |
| 3.1.0 | 5 / 0 | |
| 3.0.0 | 6 / 0 |
v3.3.10
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (oliviertassinari) than the most recent previously approved version (dmtr.kovalenko) on 2021-03-12, but oliviertassinari is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
2 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsThis file did not combine network calls with dynamic code execution in the previously greenflagged version, and now does. Gaining both halves in an existing file is a hallmark of a dropper/loader introduced by an update.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.