cldrjs — Greenflagged

Simple CLDR traverser

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

rxaviers

Keywords

utilityglobalizationinternationalizationmultilingualizationlocalizationg11ni18nm17nL10nlocalizelocalecldrjsoninheritancecompiler

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file-transition:dist/cldr.js	AI (source-diff): Standard webpack UMD bundle output, not true obfuscation; matches library's build process.	ai	2026/07/25
source-diff	obfuscated-file-transition:dist/cldr/event.js	AI (source-diff): Bundled EventEmitter dependency inlined by webpack, verified benign in sample.	ai	2026/07/25
phantom-deps	phantom-dep:wolfy87-eventemitter	AI (phantom-deps): Used inside bundled dist/cldr/event.js; import invisible to static scan post-bundling.	ai	2026/07/25
phantom-deps	phantom-dep:dco	AI (phantom-deps): DCO tooling referenced via config/build scripts, not a runtime import.	ai	2026/07/25

Versions (showing 25 of 25)

Version	Deps	Published
0.5.5	0 / 12	2020-10-22
0.5.4	0 / 12	2020-08-05
0.5.3	0 / 12	2020-08-05
0.5.2	2 / 22	2020-08-05
0.5.1	0 / 12	2019-01-21
0.5.0	0 / 12	2017-08-11
0.4.8	0 / 12	2016-11-26
0.4.7	0 / 12	2016-11-08
0.4.6	0 / 12	2016-11-07
0.4.5	0 / 12	2016-05-03
0.4.4	0 / 12	2016-01-18
0.4.3	0 / 12	2015-08-24
0.4.2	0 / 12	2015-08-23
0.4.1	0 / 12	2015-02-25
0.4.0	0 / 12	2015-01-20
0.3.11	0 / 12	2014-12-03
0.3.10	0 / 12	2014-12-02
0.3.9	0 / 11	2014-10-14
0.3.8	0 / 10	2014-07-13
0.3.7	0 / 10	2014-07-13
0.3.6	0 / 10	2014-06-24
0.3.5	0 / 8	2014-04-21
0.3.4	0 / 8	2014-04-14
0.3.3	0 / 8	2014-04-11
0.3.2	0 / 8	2014-04-08

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

3 findings

HIGH Modified file became obfuscated: dist/cldr.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

HIGH Modified file became obfuscated: dist/cldr/event.js source-diff

This file was readable in the previously greenflagged version and is now minified or obfuscated (lines over 3000 chars). A file that gains obfuscation between releases is a strong payload-swap indicator.

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.8

1 finding

LOW No provenance attestation provenance

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

v0.4.7

1 finding

LOW No provenance attestation provenance

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

v0.4.6

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.11

1 finding

LOW No provenance attestation provenance

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

v0.3.10

1 finding

LOW No provenance attestation provenance

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

v0.3.9

1 finding

LOW No provenance attestation provenance

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

v0.3.8

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.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.