@pisell/date-picker
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Actively developed UI component library; new source files reflect feature additions, not injected code. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Active multi-maintainer package; maintainer rotation is expected across 161 versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers yaoxiaojia and larry_ranhejun added alongside known publisher jinglin.tan; consistent with team expansion, not takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): @pisell/date-picker is an established internal component library with 159 versions; missing README/repo metadata is a quality issue, not a security concern. | ai | |
| dependencies | unvetted-dep:@mui/base | AI (dependencies): @mui/base is a well-known MUI library; beta version is expected for a date-picker component built on MUI ecosystem. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is declared as a runtime dep for UI component library consumers; not directly imported in source is expected for this type of package. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): MUI-based component libraries commonly declare @emotion/styled as a dependency without directly importing it in every source file. | ai | |
| phantom-deps | phantom-dep:@emotion/react | AI (phantom-deps): MUI-based component libraries commonly declare @emotion/react as a dependency without directly importing it in every source file. | ai |
Versions (showing 48 of 148)
| Version | Deps | Published |
|---|---|---|
| 1.0.47 | 14 / 2 | |
| 1.0.46 | 14 / 2 | |
| 1.0.45 | 14 / 2 | |
| 1.0.44 | 14 / 2 | |
| 1.0.43 | 14 / 2 | |
| 1.0.42 | 14 / 2 | |
| 1.0.41 | 14 / 2 | |
| 1.0.40 | 14 / 2 | |
| 1.0.39 | 14 / 2 | |
| 1.0.38 | 14 / 2 | |
| 1.0.37 | 14 / 2 | |
| 1.0.36 | 14 / 2 | |
| 1.0.35 | 14 / 2 | |
| 1.0.34 | 14 / 2 | |
| 1.0.33 | 14 / 2 | |
| 1.0.32 | 14 / 2 | |
| 1.0.31 | 14 / 2 | |
| 1.0.30 | 14 / 2 | |
| 1.0.29 | 14 / 2 | |
| 1.0.28 | 14 / 2 | |
| 1.0.27 | 14 / 2 | |
| 1.0.26 | 14 / 2 | |
| 1.0.25 | 14 / 2 | |
| 1.0.24 | 14 / 2 | |
| 1.0.23 | 14 / 2 | |
| 1.0.22 | 14 / 2 | |
| 1.0.21 | 14 / 2 | |
| 1.0.20 | 14 / 2 | |
| 1.0.19 | 14 / 2 | |
| 1.0.18 | 14 / 2 | |
| 1.0.17 | 14 / 2 | |
| 1.0.16 | 14 / 2 | |
| 1.0.15 | 14 / 2 | |
| 1.0.14 | 14 / 2 | |
| 1.0.13 | 14 / 2 | |
| 1.0.12 | 14 / 2 | |
| 1.0.11 | 14 / 2 | |
| 1.0.10 | 12 / 2 | |
| 1.0.9 | 13 / 2 | |
| 1.0.8 | 13 / 2 | |
| 1.0.7 | 13 / 2 | |
| 1.0.6 | 13 / 2 | |
| 1.0.5 | 13 / 2 | |
| 1.0.4 | 13 / 2 | |
| 1.0.3 | 13 / 2 | |
| 1.0.2 | 13 / 2 | |
| 1.0.1 | 13 / 2 | |
| 1.0.0 | 13 / 2 |
v1.0.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.