@trackunit/date-and-time-utils
The `@trackunit/date-and-time-utils` package contains basic utility functions for date and time manipulation. This library uses Temporal and other new browser API's to eliminate the need for moment.js and date-fns.
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.txt | AI (license): Custom license file pattern; stable across versions. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is not standard practice for this package; common across npm ecosystem. | ai | |
| phantom-deps | phantom-dep:@trackunit/react-test-setup | AI (phantom-deps): Declared in package.json; phantom-dep heuristic is a false positive for this package. | ai | |
| dependencies | unvetted-dep:@formatjs/intl-enumerator | AI (dependencies): Standard @formatjs intl polyfill; legitimate dependency for date/time utils. | ai | |
| dependencies | unvetted-dep:@formatjs/intl-durationformat | AI (dependencies): Standard @formatjs intl polyfill; legitimate dependency for date/time utils. | ai |
Versions (showing 9 of 314)
| Version | Deps | Published |
|---|---|---|
| 1.6.17 | 4 / 0 | |
| 1.6.16 | 4 / 0 | |
| 1.6.15 | 4 / 0 | |
| 1.6.14 | 4 / 0 | |
| 1.6.13 | 4 / 0 | |
| 1.3.128 | 4 / 0 | |
| 1.3.80 | 3 / 0 | |
| 1.3.79 | 3 / 0 | |
| 1.3.77 | 3 / 0 |
v1.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.128
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.