csv
A mature CSV toolset with simple api, full of options and tested against large datasets.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): 'csv' is a legitimate, well-established CSV parsing package with 1.9M weekly downloads — not a typosquat of 'qs'. Edit-distance match is coincidental. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): 'csv' is a legitimate, well-established CSV parsing package with 1.9M weekly downloads — not a typosquat of 'ajv'. Edit-distance match is coincidental. | ai | |
| source-diff | net-exec-file:lib/browser/index.js | AI (source-diff): Browserify bundle output; UMD wrapper triggers net+exec heuristic. Standard build artifact for this package's browser support. | ai | |
| source-diff | net-exec-file:lib/browser/sync.js | AI (source-diff): Browserify bundle output; UMD wrapper triggers net+exec heuristic. Standard build artifact for this package's browser support. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is from adding browserify browser bundles (~340KB each), as shown in the build script. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from david to GitHub Actions with SLSA provenance attestation — legitimate transition to CI/CD publishing for this established package. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 6.5.1 | 4 / 11 | |
| 6.5.0 | 4 / 11 | |
| 6.4.1 | 4 / 12 | |
| 6.4.0 | 4 / 12 | |
| 6.3.11 | 4 / 18 | |
| 6.3.10 | 4 / 15 | |
| 6.3.9 | 4 / 15 | |
| 6.3.8 | 4 / 15 | |
| 6.3.7 | 4 / 15 | |
| 6.3.6 | 4 / 15 | |
| 6.3.5 | 4 / 15 | |
| 6.3.4 | 4 / 15 | |
| 6.3.3 | 4 / 15 | |
| 6.3.2 | 4 / 15 | |
| 6.3.1 | 4 / 15 | |
| 6.3.0 | 4 / 15 | |
| 6.2.12 | 4 / 15 | |
| 6.2.11 | 4 / 15 | |
| 6.2.10 | 4 / 15 | |
| 6.2.8 | 4 / 14 | |
| 6.2.7 | 4 / 14 | |
| 6.2.6 | 4 / 14 | |
| 6.2.5 | 4 / 14 | |
| 6.2.4 | 4 / 14 | |
| 6.2.3 | 4 / 14 | |
| 6.2.2 | 4 / 14 | |
| 6.2.1 | 4 / 14 | |
| 6.2.0 | 4 / 14 | |
| 6.1.5 | 4 / 14 | |
| 6.1.4 | 4 / 14 | |
| 6.1.3 | 4 / 14 | |
| 6.1.2 | 4 / 14 | |
| 6.1.1 | 4 / 14 | |
| 6.1.0 | 4 / 14 | |
| 6.0.5 | 4 / 14 | |
| 6.0.4 | 4 / 14 | |
| 6.0.3 | 4 / 14 | |
| 6.0.2 | 4 / 14 | |
| 6.0.1 | 4 / 14 | |
| 6.0.0 | 4 / 14 | |
| 5.5.3 | 4 / 11 | |
| 5.5.2 | 4 / 11 | |
| 5.5.0 | 4 / 11 | |
| 5.4.0 | 4 / 8 | |
| 5.3.2 | 4 / 8 | |
| 5.3.1 | 4 / 8 | |
| 5.3.0 | 4 / 8 | |
| 5.2.0 | 4 / 8 | |
| 5.1.3 | 4 / 8 | |
| 5.1.2 | 4 / 8 | |
| 5.1.1 | 4 / 3 |
v6.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.5.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
3 findingsNewly 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.