CSV parsing implementing the Node.js `stream.Transform` API
88%
Total Score
healthy
Healthy release backed by recent publishing, active commits, and a maintained organization-owned repository.
The project uses npm scripts and TypeScript for builds. No security scanning tools were detected, leaving a modest security-process gap.
The repository has no security policy. This does not show unsafe code, but it reduces transparency about vulnerability reporting and response.
The single workflow analyzed successfully and had no reported audit findings or untrusted checkout/script-injection paths. However, it grants top-level write permissions and all five action references are unpinned, creating avoidable workflow supply-chain and permission hygiene concerns.
| Title | Versions | Severity |
|---|---|---|
AIKIDO-2026-149515 csv-parse is vulnerable to Prototype Pollution in versions 0.0.1 - 7.0.1. | 0.0.1 - 7.0.1 | Medium |
AIKIDO-2026-10451 Pre-CVE Found by Aikido Intel before public disclosure or CVE publication. csv-parse is vulnerable to Prototype Pollution in versions 0.0.1 - 6.2.0. | 0.0.1 - 6.2.0 | Medium |
CVE-2019-17592 csv-parse is vulnerable to Improper Input Validation in versions 0.0.0 - 4.4.6. | 0.0.0 - 4.4.6 | High |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.