@date-fns/tz
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @date-fns/tz is the official date-fns timezone package by the original date-fns author; string similarity to 'pg' is purely coincidental and not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @date-fns/tz is the official date-fns timezone package by the original date-fns author; string similarity to 'qs' is purely coincidental and not a typosquat. | ai | |
| provenance | no-provenance | AI (provenance): Established publisher (kossnocorp, original date-fns author) with strong track record; lack of provenance attestation is not a meaningful risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 0 / 0 | |
| 1.4.1 | 0 / 20 | |
| 1.4.0 | 0 / 20 | |
| 1.3.1 | 0 / 19 | |
| 1.3.0 | 0 / 19 |
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
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.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.