date-and-time
The simplest, most intuitive date and time library
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/timezone.cjs | AI (source-diff): dist/timezone.cjs is a minified timezone data file (structured GMT offset exports). Benign data bundling, not obfuscation. Stable pattern for this date/time library. | ai | |
| source-diff | obfuscated-file:dist/timezone.js | AI (source-diff): dist/timezone.js is a minified timezone data file (structured GMT offset exports). Benign data bundling, not obfuscation. Stable pattern for this date/time library. | ai | |
| source-diff | obfuscated-file:dist/timezone.d.ts | AI (source-diff): dist/timezone.d.ts is a TypeScript declaration file with timezone interface declarations. Long lines due to many declare const statements, not obfuscation. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 4.5.0 | 0 / 17 | |
| 4.4.0 | 0 / 16 | |
| 4.3.1 | 0 / 16 | |
| 4.3.0 | 0 / 16 | |
| 4.2.0 | 0 / 15 | |
| 4.1.2 | 0 / 16 | |
| 4.1.1 | 0 / 13 | |
| 4.1.0 | 0 / 13 | |
| 4.0.5 | 0 / 14 | |
| 4.0.4 | 0 / 14 | |
| 4.0.3 | 0 / 14 | |
| 4.0.2 | 0 / 14 | |
| 4.0.1 | 0 / 15 | |
| 4.0.0 | 0 / 15 | |
| 3.6.0 | 0 / 5 | |
| 3.5.0 | 0 / 5 | |
| 3.4.1 | 0 / 5 | |
| 3.4.0 | 0 / 5 | |
| 3.3.0 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.1 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.3 | 0 / 5 | |
| 3.0.2 | 0 / 5 | |
| 3.0.1 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.4.3 | 0 / 6 | |
| 2.4.2 | 0 / 6 | |
| 2.4.1 | 0 / 6 | |
| 2.4.0 | 0 / 6 | |
| 2.3.1 | 0 / 6 | |
| 2.3.0 | 0 / 6 | |
| 2.2.1 | 0 / 5 | |
| 2.2.0 | 0 / 5 | |
| 2.1.2 | 0 / 5 | |
| 2.1.1 | 0 / 5 | |
| 2.1.0 | 0 / 5 | |
| 2.0.1 | 0 / 5 | |
| 2.0.0 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.14.2 | 0 / 6 | |
| 0.14.1 | 0 / 6 | |
| 0.14.0 | 0 / 6 | |
| 0.13.1 | 0 / 6 | |
| 0.12.0 | 0 / 6 | |
| 0.11.1 | 0 / 6 | |
| 0.11.0 | 0 / 7 | |
| 0.10.0 | 0 / 7 | |
| 0.9.0 | 0 / 7 | |
| 0.8.1 | 0 / 7 |
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.