@fast-csv/format
fast-csv formatting module
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 well-known, single-purpose lodash utility with a long track record; no security concerns for this package. | ai | |
| dependencies | unvetted-dep:lodash.isfunction | AI (dependencies): lodash.isfunction is a well-known, single-purpose lodash utility with a long track record; no security concerns for this package. | ai | |
| dependencies | unvetted-dep:lodash.escaperegexp | AI (dependencies): lodash.escaperegexp is a well-known, single-purpose lodash utility with a long track record; no security concerns for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 5.0.7 | 1 / 2 | |
| 5.0.5 | 4 / 5 | |
| 5.0.2 | 5 / 6 | |
| 5.0.0 | 5 / 6 | |
| 4.3.5 | 6 / 5 | |
| 4.3.4 | 6 / 5 | |
| 4.3.3 | 6 / 5 | |
| 4.3.1 | 5 / 5 | |
| 4.3.0 | 5 / 5 | |
| 4.2.0 | 5 / 5 | |
| 4.1.5 | 5 / 5 | |
| 4.1.4 | 5 / 5 | |
| 4.1.2 | 5 / 5 | |
| 4.1.1 | 5 / 5 | |
| 4.0.3 | 5 / 5 | |
| 4.0.2 | 5 / 5 | |
| 4.0.1 | 5 / 5 | |
| 4.0.0 | 5 / 5 |
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.