← Home

json3

npm Repository Homepage

A JSON polyfill for older JavaScript platforms.

11
Versions
MIT
License
No
Install Scripts
Missing
Provenance

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

d10kitcambridge

Keywords

jsonspececmaes5lexerparserstringify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:vendor/uglifyjs/lib/parse-js.js AI (source-diff): UglifyJS parser source by Mihai Bazon; long lines from parser tables, not obfuscation. ai
source-diff large-new-source-files AI (source-diff): 99 new files are the vendored UglifyJS tree used for json3's build process; legitimate bundling. ai
source-diff net-exec-file:vendor/uglifyjs/lib/consolidator.js AI (source-diff): Vendored UglifyJS consolidator module; code execution patterns are inherent to JS parser/compressor tooling, not malware. ai
source-diff net-exec-file:vendor/uglifyjs/lib/process.js AI (source-diff): Vendored UglifyJS AST processor; eval-like constructs are inherent to code generation tooling. ai
source-diff net-exec-file:vendor/uglifyjs/test/testparser.js AI (source-diff): Vendored UglifyJS test file using require('sys') and parseJS; standard test harness, not malware. ai
source-diff obfuscated-file:coverage/lcov-report/prettify.js AI (source-diff): This is Google Code Prettify, a standard file bundled by Istanbul/nyc lcov HTML coverage reports. Not obfuscated malicious code. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is in benchmark/benchmark_json3.js, a benchmark harness. Standard pattern for loading competing implementations; not production code. ai
source-diff net-exec-file:benchmark/assets/html5.js AI (source-diff): File is the HTML5 Shiv polyfill in benchmark/assets/ — dev/benchmark tooling only, not on any production code path. Pattern is DOM shim logic, not malware. ai

Versions (showing 11 of 11)

Version Deps Published
3.3.3 0 / 6
3.3.2 0 / 0
3.3.1 0 / 0
3.3.0 0 / 0
3.2.6 0 / 0
3.2.5 0 / 0
3.2.4 0 / 0
3.2.2 0 / 0
3.2.1 0 / 0
3.2.0 0 / 0
3.1.0 0 / 0

v3.3.3

1 finding
LOW No provenance attestation provenance

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

v3.3.2

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

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

2 findings
HIGH New obfuscated file: coverage/lcov-report/prettify.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.

LOW No provenance attestation provenance

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

v3.2.5

2 findings
HIGH New file with network + code execution: benchmark/assets/html5.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v3.2.4

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.1

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

5 findings
HIGH New file with network + code execution: vendor/uglifyjs/lib/consolidator.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New obfuscated file: vendor/uglifyjs/lib/parse-js.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 file with network + code execution: vendor/uglifyjs/lib/process.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: vendor/uglifyjs/test/testparser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.