@formatjs/intl-utils — Greenflagged

Smartly determine best unit for relative time format

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

longlhopyrocatredonkulus

Keywords

intli18nrelativemomentformatdate

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from longlho to pyrocat occurred in Jan 2020; pyrocat has 815 approved packages and is a trusted maintainer within the formatjs org. This is a stable historical transition.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): pyrocat is a long-standing trusted publisher with 815 approved packages; the maintainer addition is a legitimate historical transition within the formatjs ecosystem.	ai	2026/04/24
source-diff	obfuscated-file:dist/aliases.js	AI (source-diff): Auto-generated CLDR locale alias lookup table; long lines are data (key-value pairs), not obfuscated code. Marked @generated with prettier-ignore. Stable false positive for this i18n package.	ai	2026/04/24
source-diff	obfuscated-file:lib/aliases.js	AI (source-diff): Same auto-generated CLDR locale alias data as dist/aliases.js; ESM variant. Stable false positive for this i18n package.	ai	2026/04/24
source-diff	obfuscated-file:src/aliases.ts	AI (source-diff): TypeScript source of the same auto-generated CLDR locale alias data. Long lines are data, not obfuscation. Stable false positive for this i18n package.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
3.8.4	1 / 0	2020-08-17
3.8.3	1 / 0	2020-08-14
3.8.2	1 / 0	2020-07-24
3.8.1	1 / 0	2020-07-16
3.8.0	1 / 0	2020-07-14
3.7.0	1 / 0	2020-07-14
3.6.0	1 / 2	2020-07-03
3.5.0	1 / 2	2020-07-01
3.4.1	1 / 2	2020-06-23
3.4.0	1 / 2	2020-06-20
3.3.1	1 / 2	2020-06-04
3.3.0	1 / 2	2020-06-04
3.2.0	0 / 2	2020-06-03
3.1.0	0 / 2	2020-05-25
3.0.1	0 / 6	2020-05-23
3.0.0	0 / 6	2020-05-23
2.3.0	0 / 6	2020-05-16
2.2.5	0 / 6	2020-05-05
2.2.4	0 / 6	2020-04-28
2.2.3	0 / 0	2020-04-24
2.2.2	0 / 0	2020-04-14
2.2.1	0 / 0	2020-03-30
2.2.0	0 / 0	2020-01-27
2.1.0	0 / 0	2020-01-22
2.0.4	0 / 0	2020-01-09
2.0.3	0 / 0	2020-01-08
2.0.2	0 / 0	2020-01-06
2.0.1	0 / 0	2019-12-27
2.0.0	0 / 0	2019-12-26

v3.8.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.8.3

1 finding

LOW No provenance attestation provenance

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

v3.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.1

4 findings

HIGH New obfuscated file: dist/aliases.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: lib/aliases.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: src/aliases.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.

v3.3.0

4 findings

HIGH New obfuscated file: dist/aliases.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: lib/aliases.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: src/aliases.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.

v3.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.5

1 finding

LOW No provenance attestation provenance

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

v2.2.4

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

2 findings

HIGH Publisher changed: longlho → pyrocat (on 2020-03-30) provenance

This version was published by a different npm account than previous versions on 2020-03-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.2.0

2 findings

HIGH Publisher changed: longlho → pyrocat (on 2020-01-27) provenance

This version was published by a different npm account than previous versions on 2020-01-27. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.