csv-generate — Greenflagged

CSV and object generation implementing the Node.js `stream.Readable` API

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

david

Keywords

streamgeneratecsvobjectbackendfrontend

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:lib/browser/index.js	AI (source-diff): Browserify bundle output from documented build:browserify script; standard UMD wrapper, no actual network/exec payload.	ai	2026/04/24
source-diff	net-exec-file:lib/browser/sync.js	AI (source-diff): Browserify bundle output from documented build:browserify script; standard UMD wrapper, no actual network/exec payload.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from two ~260KB browserify browser bundles added in this version; expected for browser support.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Transition from manual (david) to CI/CD (GitHub Actions) publishing with SLSA provenance from the correct adaltas/node-csv repo. Legitimate modernization.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Mature stable package with infrequent releases; 250-day gap is normal. SLSA provenance confirms legitimate origin.	ai	2026/04/23

Versions (showing 50 of 50)

Version	Deps	Published
4.5.1	0 / 12	2026-03-17
4.5.0	0 / 13	2025-07-10
4.4.2	0 / 18	2024-11-21
4.4.1	0 / 15	2024-05-13
4.4.0	0 / 15	2024-02-27
4.3.1	0 / 15	2023-12-08
4.3.0	0 / 15	2023-10-05
4.2.8	0 / 15	2023-08-25
4.2.7	0 / 15	2023-08-24
4.2.6	0 / 15	2023-05-04
4.2.5	0 / 15	2023-04-30
4.2.4	0 / 15	2023-04-16
4.2.2	0 / 15	2023-02-08
4.2.1	0 / 15	2022-11-08
4.2.0	0 / 15	2022-07-10
4.1.0	0 / 15	2022-05-24
4.0.4	0 / 15	2021-12-29
4.0.3	0 / 15	2021-11-19
4.0.2	0 / 15	2021-11-18
4.0.1	0 / 15	2021-11-15
4.0.0	0 / 15	2021-11-15
3.4.3	0 / 14	2021-09-03
3.4.2	0 / 14	2021-08-27
3.4.0	0 / 14	2021-04-03
3.3.0	0 / 12	2020-11-16
3.2.4	0 / 12	2019-12-04
3.2.3	0 / 11	2019-05-13
3.2.2	0 / 11	2019-05-13
3.2.1	0 / 11	2019-05-13
3.2.0	0 / 11	2018-11-28
3.1.0	0 / 6	2018-11-19
3.0.0	0 / 6	2018-10-24
2.2.2	0 / 6	2018-09-29
2.2.1	0 / 6	2018-09-28
2.2.0	0 / 6	2018-09-28
2.1.0	0 / 5	2018-07-23
2.0.2	0 / 5	2018-02-15
2.0.1	2 / 3	2018-02-14
2.0.0	0 / 3	2017-10-20
1.1.2	0 / 3	2017-10-20
1.1.1	0 / 3	2017-10-20
1.1.0	0 / 3	2017-10-20
1.0.0	0 / 3	2015-10-07
0.0.6	0 / 3	2015-06-09
0.0.5	0 / 3	2015-05-29
0.0.4	0 / 3	2014-05-09
0.0.3	0 / 3	2014-05-02
0.0.2	0 / 3	2014-05-01
0.0.1	0 / 3	2014-03-22
0.0.0	0 / 3	2014-03-17

v4.5.1

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.

v4.5.0

1 finding

LOW No provenance attestation provenance

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

v4.4.2

1 finding

LOW No provenance attestation provenance

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

v4.4.1

1 finding

LOW No provenance attestation provenance

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

v4.4.0

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.2.8

1 finding

LOW No provenance attestation provenance

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

v4.2.7

1 finding

LOW No provenance attestation provenance

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

v4.2.6

1 finding

LOW No provenance attestation provenance

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

v4.2.5

1 finding

LOW No provenance attestation provenance

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

v4.2.4

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.4

1 finding

LOW No provenance attestation provenance

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

v4.0.3

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

v4.0.1

1 finding

LOW No provenance attestation provenance

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

v4.0.0

1 finding

LOW No provenance attestation provenance

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

v3.4.3

1 finding

LOW No provenance attestation provenance

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

v3.4.2

1 finding

LOW No provenance attestation provenance

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

v3.4.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.

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.4

1 finding

LOW No provenance attestation provenance

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

v3.2.3

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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