csvtojson
2
Versions
—
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
keyang
Keywords
csvcsv parserparse csvcsvtojsonjsoncsv to jsoncsv converttojsonconvert csv to jsoncsv-json
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Occurs in webpack-bundled browser.js; new Function() is standard webpack module loader infrastructure, not malicious dynamic code execution. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): v1/core/workerMgr.js spawns process.execPath with a local worker.js for CSV parsing parallelism — legitimate worker process pattern, not arbitrary command execution. | ai | |
| provenance | no-provenance | AI (provenance): Established package (4695 days old, 86 versions); lack of Sigstore provenance is common and not a risk signal here. | ai |
v2.0.14
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.0.13
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.