@trackunit/react-date-and-time-hooks
This library contains React Hooks used to manipulate dates such as: - Subtracting days, weeks or months - Adding days, weeks or months - Finding the start and end of days, weeks, months - Finding differences between two dates - See if a date is in the fut
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Config-file reference; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@trackunit/react-test-setup | AI (phantom-deps): Same-org scoped package; test dependency pattern. | ai | |
| phantom-deps | phantom-dep:@trackunit/iris-app-build-utilities | AI (phantom-deps): Same-org scoped package; build utility pattern. | ai | |
| phantom-deps | phantom-dep:@trackunit/react-core-contexts-test | AI (phantom-deps): Same-org test utility; declared as dep but not directly imported — typical monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/cli | AI (phantom-deps): Build/codegen tool referenced in config files, not runtime imports — stable false positive for this package. | ai |
Versions (showing 100 of 722)
| Version | Deps | Published |
|---|---|---|
| 1.3.102 | 14 / 0 | |
| 1.3.101 | 14 / 0 | |
| 1.3.100 | 14 / 0 | |
| 1.3.98 | 14 / 0 | |
| 1.3.97 | 14 / 0 | |
| 1.3.95 | 14 / 0 | |
| 1.3.94 | 14 / 0 | |
| 1.3.93 | 14 / 0 | |
| 1.3.92 | 14 / 0 | |
| 1.3.91 | 14 / 0 | |
| 1.3.90 | 14 / 0 | |
| 1.3.89 | 14 / 0 | |
| 1.3.87 | 14 / 0 | |
| 1.3.85 | 14 / 0 | |
| 1.3.84 | 14 / 0 | |
| 1.3.83 | 14 / 0 | |
| 1.3.81 | 14 / 0 | |
| 1.3.80 | 14 / 0 | |
| 1.3.79 | 14 / 0 | |
| 1.3.78 | 14 / 0 | |
| 1.3.76 | 14 / 0 | |
| 1.3.75 | 14 / 0 | |
| 1.3.74 | 14 / 0 | |
| 1.3.72 | 14 / 0 | |
| 1.3.70 | 14 / 0 | |
| 1.3.69 | 14 / 0 | |
| 1.3.68 | 14 / 0 | |
| 1.3.66 | 14 / 0 | |
| 1.3.65 | 14 / 0 | |
| 1.3.64 | 14 / 0 | |
| 1.3.63 | 14 / 0 | |
| 1.3.62 | 14 / 0 | |
| 1.3.60 | 14 / 0 | |
| 1.3.59 | 14 / 0 | |
| 1.3.58 | 14 / 0 | |
| 1.3.57 | 14 / 0 | |
| 1.3.56 | 14 / 0 | |
| 1.3.55 | 14 / 0 | |
| 1.3.54 | 14 / 0 | |
| 1.3.53 | 14 / 0 | |
| 1.3.52 | 14 / 0 | |
| 1.3.51 | 14 / 0 | |
| 1.3.50 | 14 / 0 | |
| 1.3.48 | 14 / 0 | |
| 1.3.47 | 14 / 0 | |
| 1.3.45 | 14 / 0 | |
| 1.3.44 | 14 / 0 | |
| 1.3.43 | 14 / 0 | |
| 1.3.42 | 14 / 0 | |
| 1.3.41 | 14 / 0 | |
| 1.3.40 | 14 / 0 | |
| 1.3.38 | 14 / 0 | |
| 1.3.37 | 14 / 0 | |
| 1.3.36 | 14 / 0 | |
| 1.3.35 | 14 / 0 | |
| 1.3.34 | 14 / 0 | |
| 1.3.33 | 14 / 0 | |
| 1.3.31 | 14 / 0 | |
| 1.3.30 | 14 / 0 | |
| 1.3.29 | 14 / 0 | |
| 1.3.28 | 14 / 0 | |
| 1.3.24 | 14 / 0 | |
| 1.3.22 | 14 / 0 | |
| 1.3.21 | 14 / 0 | |
| 1.3.19 | 14 / 0 | |
| 1.3.18 | 14 / 0 | |
| 1.3.17 | 14 / 0 | |
| 1.3.15 | 14 / 0 | |
| 1.3.14 | 14 / 0 | |
| 1.3.13 | 14 / 0 | |
| 1.3.11 | 14 / 0 | |
| 1.3.10 | 14 / 0 | |
| 1.3.9 | 14 / 0 | |
| 1.3.8 | 14 / 0 | |
| 1.3.7 | 14 / 0 | |
| 1.3.6 | 14 / 0 | |
| 1.3.5 | 14 / 0 | |
| 1.3.4 | 14 / 0 | |
| 1.3.2 | 14 / 0 | |
| 1.3.1 | 14 / 0 | |
| 1.2.1 | 14 / 0 | |
| 1.2.0 | 14 / 0 | |
| 1.1.1 | 14 / 0 | |
| 1.1.0 | 14 / 0 | |
| 1.0.66 | 14 / 0 | |
| 1.0.60 | 14 / 0 | |
| 1.0.58 | 14 / 0 | |
| 1.0.56 | 14 / 0 | |
| 1.0.55 | 14 / 0 | |
| 1.0.53 | 14 / 0 | |
| 1.0.52 | 14 / 0 | |
| 1.0.49 | 14 / 0 | |
| 1.0.48 | 14 / 0 | |
| 1.0.47 | 14 / 0 | |
| 1.0.45 | 14 / 0 | |
| 1.0.43 | 14 / 0 | |
| 1.0.42 | 14 / 0 | |
| 1.0.36 | 14 / 0 | |
| 1.0.35 | 14 / 0 | |
| 1.0.33 | 14 / 0 |
v1.3.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.45
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.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.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.