@trackunit/react-date-and-time-components
This package exposes the Trackunit date and time ui components. The ui components from this package is used by the Trackunit Manager as well as the Iris App SDK.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established @trackunit monorepo publisher; lack of Sigstore provenance is consistent across all their packages. | ai |
Versions (showing 51 of 839)
| Version | Deps | Published |
|---|---|---|
| 2.2.23 | 11 / 0 | |
| 2.2.22 | 11 / 0 | |
| 2.2.21 | 11 / 0 | |
| 2.2.20 | 11 / 0 | |
| 2.2.19 | 11 / 0 | |
| 2.2.17 | 11 / 0 | |
| 2.2.15 | 11 / 0 | |
| 2.2.9 | 11 / 0 | |
| 2.2.8 | 11 / 0 | |
| 2.2.7 | 11 / 0 | |
| 2.2.6 | 11 / 0 | |
| 2.2.5 | 11 / 0 | |
| 2.2.4 | 11 / 0 | |
| 2.2.3 | 11 / 0 | |
| 2.2.2 | 11 / 0 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 | |
| 2.1.69 | 11 / 0 | |
| 2.1.68 | 11 / 0 | |
| 2.1.67 | 11 / 0 | |
| 2.1.66 | 11 / 0 | |
| 2.1.65 | 11 / 0 | |
| 2.1.64 | 11 / 0 | |
| 2.1.63 | 11 / 0 | |
| 2.1.62 | 11 / 0 | |
| 2.1.61 | 11 / 0 | |
| 2.1.60 | 11 / 0 | |
| 2.1.59 | 11 / 0 | |
| 2.1.58 | 11 / 0 | |
| 2.1.56 | 11 / 0 | |
| 2.1.55 | 11 / 0 | |
| 2.1.53 | 11 / 0 | |
| 2.1.52 | 11 / 0 | |
| 2.1.51 | 11 / 0 | |
| 2.1.50 | 11 / 0 | |
| 2.1.49 | 11 / 0 | |
| 2.1.48 | 11 / 0 | |
| 2.1.47 | 11 / 0 | |
| 2.1.46 | 11 / 0 | |
| 2.1.44 | 11 / 0 | |
| 2.1.43 | 11 / 0 | |
| 2.1.42 | 11 / 0 | |
| 2.1.41 | 11 / 0 | |
| 2.1.39 | 11 / 0 | |
| 2.1.38 | 11 / 0 | |
| 2.1.37 | 11 / 0 | |
| 2.1.36 | 11 / 0 | |
| 2.1.35 | 11 / 0 | |
| 2.1.34 | 11 / 0 | |
| 2.1.33 | 11 / 0 | |
| 2.1.32 | 11 / 0 |
v2.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.