globalize
A JavaScript library for internationalization and localization that leverages the official Unicode CLDR JSON data.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:examples/app-bower-grunt-requirejs/bower_components/react/JSXTransformer.js | AI (source-diff): Legitimate vendored Facebook React JSXTransformer bundled in example app, not injected code. | ai | |
| source-diff | net-exec-file:examples/app-bower-grunt-requirejs/bower_components/react/JSXTransformer.js | AI (source-diff): eval() is React's own JSX-to-JS transform, not a dropper. | ai | |
| source-diff | net-exec-file:examples/app-bower-grunt-requirejs/bower_components/requirejs/require.js | AI (source-diff): Vendored RequireJS AMD loader in example app; standard library code. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval used inside React's official JSXTransformer, documented and expected. | ai | |
| vendored-integrity | unresolved-vendored-tree:examples/app-bower-grunt-requirejs/bower_components/almond | AI (vendored-integrity): Bower-vendored example dependency, unrelated to package runtime. | ai | |
| vendored-integrity | unresolved-vendored-tree:examples/app-bower-grunt-requirejs/bower_components/cldrjs | AI (vendored-integrity): Bower-vendored example dependency, unrelated to package runtime. | ai | |
| vendored-integrity | unresolved-vendored-tree:examples/app-bower-grunt-requirejs/bower_components/globalize | AI (vendored-integrity): Self-referential vendored copy for example app, not runtime code. | ai | |
| vendored-integrity | unresolved-vendored-tree:examples/app-bower-grunt-requirejs/bower_components/react | AI (vendored-integrity): Vendored React copy for example app demo purposes. | ai | |
| vendored-integrity | unresolved-vendored-tree:examples/app-bower-grunt-requirejs/bower_components/requirejs-text | AI (vendored-integrity): Vendored text plugin for RequireJS example app. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.7.1 | 1 / 26 | |
| 1.7.0 | 1 / 25 | |
| 1.6.0 | 1 / 24 | |
| 1.5.0 | 1 / 24 | |
| 1.4.3 | 1 / 24 | |
| 1.4.0 | 1 / 24 | |
| 1.3.0 | 1 / 24 | |
| 1.2.3 | 1 / 17 | |
| 1.2.2 | 1 / 17 | |
| 1.2.1 | 1 / 17 | |
| 1.2.0 | 1 / 17 | |
| 1.1.2 | 1 / 17 | |
| 1.1.1 | 1 / 16 | |
| 1.1.0 | 1 / 16 | |
| 1.0.1 | 1 / 16 | |
| 1.0.0 | 1 / 15 |
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
6 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. Source: https://github.com/jquery/globalize/blob/85991ac658806ed39ce04c0cd35c708cd67756ef/examples/app-bower-grunt-requirejs/bower_components/react/JSXTransformer.js#L62 60 | */ 61 | function exec(source, options) { > 62 | return eval(transformReact(source, options).code); 63 | } 64 |
eval() can execute arbitrary code — common in supply-chain attacks but also used by legitimate parsers and template engines. Verify the input source. Source: https://github.com/jquery/globalize/blob/85991ac658806ed39ce04c0cd35c708cd67756ef/examples/app-bower-grunt-requirejs/bower_components/requirejs/require.js#L2098 2096 | req.exec = function (text) { 2097 | /*jslint evil: true */ > 2098 | return eval(text); 2099 | }; 2100 |
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.