@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 — 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 |
|---|---|---|---|---|
| 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 58 of 567)
| Version | Deps | Published |
|---|---|---|
| 1.3.161 | 15 / 0 | |
| 1.3.155 | 15 / 0 | |
| 1.3.154 | 15 / 0 | |
| 1.3.153 | 15 / 0 | |
| 1.3.151 | 15 / 0 | |
| 1.3.150 | 15 / 0 | |
| 1.3.149 | 15 / 0 | |
| 1.3.148 | 15 / 0 | |
| 1.3.147 | 15 / 0 | |
| 1.3.146 | 15 / 0 | |
| 1.3.145 | 15 / 0 | |
| 1.3.144 | 15 / 0 | |
| 1.3.143 | 15 / 0 | |
| 1.3.142 | 15 / 0 | |
| 1.3.141 | 15 / 0 | |
| 1.3.140 | 15 / 0 | |
| 1.3.139 | 15 / 0 | |
| 1.3.138 | 15 / 0 | |
| 1.3.137 | 15 / 0 | |
| 1.3.136 | 15 / 0 | |
| 1.3.135 | 15 / 0 | |
| 1.3.134 | 15 / 0 | |
| 1.3.133 | 15 / 0 | |
| 1.3.131 | 15 / 0 | |
| 1.3.130 | 15 / 0 | |
| 1.3.129 | 15 / 0 | |
| 1.3.127 | 15 / 0 | |
| 1.3.126 | 14 / 0 | |
| 1.3.124 | 14 / 0 | |
| 1.3.123 | 14 / 0 | |
| 1.3.122 | 14 / 0 | |
| 1.3.121 | 14 / 0 | |
| 1.3.120 | 14 / 0 | |
| 1.3.119 | 14 / 0 | |
| 1.3.117 | 14 / 0 | |
| 1.3.115 | 14 / 0 | |
| 1.3.114 | 14 / 0 | |
| 1.3.113 | 14 / 0 | |
| 1.3.112 | 14 / 0 | |
| 1.3.111 | 14 / 0 | |
| 1.3.109 | 14 / 0 | |
| 1.3.108 | 14 / 0 | |
| 1.3.105 | 14 / 0 | |
| 1.3.104 | 14 / 0 | |
| 1.3.103 | 14 / 0 | |
| 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 |
v1.3.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.155
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.154
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.153
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.151
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.150
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.149
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.148
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.147
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.146
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.145
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.144
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.143
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.142
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.141
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.140
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.139
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.138
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.137
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.136
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.135
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.123
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.122
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.120
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.119
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.94
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.