date-and-time — Greenflagged

The simplest, most intuitive date and time library

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

knowledgecode

Keywords

datedatetimedurationformatparsetimetimezone

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	2026/04/23
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	2026/04/23
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	2026/04/23

Versions (showing 73 of 73)

Version	Deps	Published
4.5.0	0 / 17	2026-05-06
4.4.0	0 / 16	2026-03-29
4.3.1	0 / 16	2026-03-07
4.3.0	0 / 16	2026-02-23
4.2.0	0 / 15	2026-01-18
4.1.2	0 / 16	2025-12-14
4.1.1	0 / 13	2025-11-17
4.1.0	0 / 13	2025-10-08
4.0.5	0 / 14	2025-09-12
4.0.4	0 / 14	2025-09-01
4.0.3	0 / 14	2025-08-28
4.0.2	0 / 14	2025-08-13
4.0.1	0 / 15	2025-07-30
4.0.0	0 / 15	2025-07-30
3.6.0	0 / 5	2024-09-28
3.5.0	0 / 5	2024-08-14
3.4.1	0 / 5	2024-07-13
3.4.0	0 / 5	2024-07-07
3.3.0	0 / 5	2024-05-19
3.2.0	0 / 5	2024-05-06
3.1.1	0 / 5	2024-01-14
3.1.0	0 / 5	2024-01-06
3.0.3	0 / 5	2023-09-16
3.0.2	0 / 5	2023-06-18
3.0.1	0 / 5	2023-06-11
3.0.0	0 / 5	2023-04-23
2.4.3	0 / 6	2023-03-15
2.4.2	0 / 6	2023-01-13
2.4.1	0 / 6	2022-07-24
2.4.0	0 / 6	2022-06-23
2.3.1	0 / 6	2022-04-10
2.3.0	0 / 6	2022-03-11
2.2.1	0 / 5	2022-02-27
2.2.0	0 / 5	2022-02-26
2.1.2	0 / 5	2022-02-14
2.1.1	0 / 5	2022-02-10
2.1.0	0 / 5	2022-01-11
2.0.1	0 / 5	2021-10-03
2.0.0	0 / 5	2021-08-13
1.0.1	0 / 5	2021-05-31
1.0.0	0 / 5	2021-04-05
0.14.2	0 / 6	2020-12-24
0.14.1	0 / 6	2020-08-23
0.14.0	0 / 6	2020-08-04
0.13.1	0 / 6	2020-03-16
0.12.0	0 / 6	2020-01-12
0.11.1	0 / 6	2019-12-14
0.11.0	0 / 7	2019-11-18
0.10.0	0 / 7	2019-09-18
0.9.0	0 / 7	2019-08-01
0.8.1	0 / 7	2019-07-11
0.7.0	0 / 7	2019-06-03
0.6.3	0 / 7	2018-10-25
0.6.2	0 / 7	2018-01-08
0.6.1	0 / 7	2017-11-29
0.5.0	0 / 7	2017-07-03
0.4.2	0 / 4	2017-06-18
0.4.1	0 / 4	2017-06-15
0.4.0	0 / 4	2016-11-14
0.3.0	0 / 4	2016-01-30
0.2.3	0 / 4	2016-01-23
0.2.2	0 / 4	2016-01-18
0.2.1	0 / 4	2016-01-14
0.2.0	0 / 4	2016-01-11
0.1.8	0 / 3	2015-06-22
0.1.7	0 / 3	2015-04-17
0.1.6	0 / 4	2015-01-25
0.1.5	0 / 4	2015-01-18
0.1.4	0 / 4	2015-01-11
0.1.3	0 / 4	2015-01-04
0.1.2	0 / 4	2015-01-03
0.1.1	0 / 4	2015-01-03
0.1.0	0 / 4	2015-01-03

v4.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.3.0

4 findings

HIGH New obfuscated file: dist/timezone.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/timezone.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/timezone.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.2.0

4 findings

HIGH New obfuscated file: dist/timezone.cjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/timezone.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/timezone.d.ts source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.