@fast-csv/parse
fast-csv parsing package
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:lodash.isnil | AI (dependencies): lodash.isnil is a stable, well-known lodash utility sub-package with a long npm history; unvetted status is a registry artifact, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:lodash.groupby | AI (dependencies): lodash.groupby is a stable, well-known lodash utility sub-package; unvetted status is a registry artifact, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:lodash.isfunction | AI (dependencies): lodash.isfunction is a stable, well-known lodash utility sub-package; unvetted status is a registry artifact, not a security concern for this package. | ai | |
| dependencies | unvetted-dep:lodash.escaperegexp | AI (dependencies): lodash.escaperegexp is a stable, well-known lodash utility sub-package; unvetted status is a registry artifact, not a security concern for this package. | ai | |
| typosquat | typosquat.levenshtein:parcel | AI (typosquat): @fast-csv/parse is the official C2FO fast-csv CSV parsing package with 6+ years of history; similarity to 'parcel' is coincidental and not a typosquat. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.0.7 | 3 / 8 | |
| 5.0.5 | 6 / 11 | |
| 5.0.2 | 6 / 11 | |
| 5.0.0 | 6 / 11 | |
| 4.3.6 | 7 / 10 |
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.