csv — Greenflagged

A mature CSV toolset with simple api, full of options and tested against large datasets.

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

david

Keywords

nodecsvtsvparserparsestringifierstringifytransformstreamgenerategenerationbackendfrontend

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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/24
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	2026/04/23

Versions (showing 100 of 104)

Version	Deps	Published
6.5.1	4 / 11	2026-03-20
6.5.0	4 / 11	2026-03-17
6.4.1	4 / 12	2025-07-16
6.4.0	4 / 12	2025-07-10
6.3.11	4 / 18	2024-11-21
6.3.10	4 / 15	2024-07-27
6.3.9	4 / 15	2024-05-13
6.3.8	4 / 15	2024-02-28
6.3.7	4 / 15	2024-02-27
6.3.6	4 / 15	2023-12-08
6.3.5	4 / 15	2023-10-09
6.3.4	4 / 15	2023-10-05
6.3.3	4 / 15	2023-08-25
6.3.2	4 / 15	2023-08-24
6.3.1	4 / 15	2023-05-26
6.3.0	4 / 15	2023-05-09
6.2.12	4 / 15	2023-05-04
6.2.11	4 / 15	2023-04-30
6.2.10	4 / 15	2023-04-16
6.2.8	4 / 14	2023-03-04
6.2.7	4 / 14	2023-02-08
6.2.6	4 / 14	2023-01-31
6.2.5	4 / 14	2022-11-30
6.2.4	4 / 14	2022-11-28
6.2.3	4 / 14	2022-11-22
6.2.2	4 / 14	2022-11-08
6.2.1	4 / 14	2022-10-12
6.2.0	4 / 14	2022-07-10
6.1.5	4 / 14	2022-07-01
6.1.4	4 / 14	2022-06-29
6.1.3	4 / 14	2022-06-16
6.1.2	4 / 14	2022-06-14
6.1.1	4 / 14	2022-06-14
6.1.0	4 / 14	2022-05-24
6.0.5	4 / 14	2021-12-29
6.0.4	4 / 14	2021-11-19
6.0.3	4 / 14	2021-11-19
6.0.2	4 / 14	2021-11-18
6.0.1	4 / 14	2021-11-15
6.0.0	4 / 14	2021-11-15
5.5.3	4 / 11	2021-09-03
5.5.2	4 / 11	2021-08-27
5.5.0	4 / 11	2021-04-03
5.4.0	4 / 8	2021-03-10
5.3.2	4 / 8	2020-03-03
5.3.1	4 / 8	2019-12-04
5.3.0	4 / 8	2019-11-15
5.2.0	4 / 8	2019-11-15
5.1.3	4 / 8	2019-09-20
5.1.2	4 / 8	2019-08-10
5.1.1	4 / 3	2019-01-10
5.1.0	4 / 6	2018-12-30
5.0.1	4 / 6	2018-12-17
5.0.0	4 / 6	2018-11-21
4.0.0	4 / 6	2018-10-01
3.1.0	4 / 1	2018-05-17
3.0.2	4 / 1	2018-04-09
3.0.1	4 / 1	2018-04-09
3.0.0	4 / 1	2018-04-06
2.0.0	4 / 1	2017-10-20
1.2.1	4 / 0	2017-10-20
1.2.0	4 / 0	2017-10-20
1.1.1	4 / 0	2017-01-26
1.1.0	4 / 0	2016-05-19
0.4.6	4 / 0	2015-08-10
0.4.5	4 / 0	2015-06-11
0.4.4	4 / 0	2015-06-09
0.4.2	4 / 0	2015-04-22
0.4.1	4 / 0	2014-10-30
0.4.0	4 / 0	2014-05-19
0.3.7	0 / 6	2014-01-29
0.3.6	0 / 6	2013-08-15
0.3.5	0 / 6	2013-07-30
0.3.4	0 / 6	2013-07-24
0.3.3	0 / 6	2013-06-13
0.3.2	0 / 6	2013-05-29
0.3.0	0 / 6	2013-04-10
0.2.9	0 / 6	2013-03-17
0.2.8	0 / 6	2013-03-13
0.2.7	0 / 5	2013-02-09
0.2.6	0 / 6	2013-01-02
0.2.4	0 / 6	2012-11-20
0.2.3	0 / 6	2012-11-16
0.2.2	0 / 6	2012-11-05
0.2.1	0 / 6	2012-10-24
0.2.0	0 / 6	2012-10-02
0.1.0	0 / 3	2012-11-19
0.0.19	0 / 3	2012-08-15
0.0.18	0 / 3	2012-07-26
0.0.17	0 / 3	2012-07-20
0.0.16	0 / 3	2012-07-01
0.0.15	0 / 3	2012-06-20
0.0.14	0 / 3	2012-06-20
0.0.13	0 / 3	2012-04-03
0.0.12	0 / 3	2012-04-01
0.0.11	0 / 0	2012-02-12
0.0.10	0 / 0	2011-09-05
0.0.9	0 / 0	2011-04-10
0.0.7	0 / 0	2011-02-14
0.0.6	0 / 0	2011-01-27

Showing 100 of 104 Next page →

v6.5.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.5.0

2 findings

HIGH Publisher changed: david → GitHub Actions (on 2026-03-17) provenance

This 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.

INFO Has SLSA provenance attestation provenance

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 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.5.2

3 findings

HIGH New file with network + code execution: lib/browser/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: lib/browser/sync.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.5.0

3 findings

HIGH New file with network + code execution: lib/browser/index.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: lib/browser/sync.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.1

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.

v5.1.0

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.

v5.0.1

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.

v5.0.0

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.