stream-transform — Greenflagged

Object transformations implementing the Node.js `stream.Transform` API

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

david

Keywords

streamtransformcsvobjectbackendfrontend

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 generated by build:browserify script; standard UMD wrapper triggers false positive on network+exec pattern.	ai	2026/04/24
source-diff	net-exec-file:lib/browser/sync.js	AI (source-diff): Browserify bundle generated by build:browserify script; standard UMD wrapper triggers false positive on network+exec pattern.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from two ~265KB Browserify browser bundles added in this version; expected for browser build support.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Transition from personal npm account (david) to GitHub Actions CI/CD publishing is documented by SLSA provenance attestation; consistent with adaltas org's move to automated releases.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): stream-transform is part of the adaltas/node-csv monorepo; infrequent but legitimate maintenance publishes are expected for this stable utility package.	ai	2026/04/23

Versions (showing 51 of 51)

Version	Deps	Published
3.4.1	0 / 14	2026-03-17
3.4.0	0 / 15	2025-07-10
3.3.3	0 / 20	2024-11-21
3.3.2	0 / 16	2024-05-13
3.3.1	0 / 16	2024-02-27
3.3.0	0 / 16	2023-12-08
3.2.10	0 / 16	2023-10-09
3.2.9	0 / 16	2023-10-05
3.2.8	0 / 16	2023-08-25
3.2.7	0 / 16	2023-08-24
3.2.6	0 / 16	2023-05-04
3.2.5	0 / 16	2023-04-30
3.2.4	0 / 16	2023-04-16
3.2.2	0 / 16	2023-02-08
3.2.1	0 / 16	2022-11-08
3.2.0	0 / 16	2022-07-10
3.1.0	0 / 16	2022-05-24
3.0.4	0 / 16	2021-12-29
3.0.3	0 / 16	2021-11-19
3.0.2	0 / 16	2021-11-18
3.0.1	0 / 16	2021-11-15
3.0.0	0 / 16	2021-11-15
2.1.3	1 / 15	2021-09-03
2.1.2	1 / 15	2021-08-27
2.1.0	1 / 15	2021-04-03
2.0.4	1 / 14	2020-12-15
2.0.3	1 / 14	2020-11-16
2.0.2	1 / 14	2020-05-04
2.0.1	1 / 13	2019-06-08
2.0.0	1 / 13	2019-04-25
1.0.8	0 / 8	2018-12-07
1.0.7	0 / 8	2018-09-29
1.0.6	0 / 8	2018-09-28
1.0.5	0 / 8	2018-09-28
1.0.4	0 / 7	2018-09-25
1.0.3	0 / 7	2018-09-24
1.0.2	0 / 7	2018-02-15
1.0.1	2 / 5	2018-02-14
1.0.0	0 / 5	2017-10-20
0.2.2	0 / 5	2017-10-20
0.2.1	0 / 5	2017-10-20
0.2.0	0 / 5	2017-10-20
0.1.2	0 / 5	2017-02-07
0.1.1	0 / 5	2015-10-20
0.1.0	0 / 5	2015-06-10
0.0.9	0 / 5	2015-06-09
0.0.8	0 / 5	2015-05-29
0.0.7	0 / 5	2015-02-27
0.0.6	0 / 5	2014-08-07
0.0.4	0 / 5	2014-06-22
0.0.2	0 / 5	2014-04-28

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

v3.4.0

1 finding

LOW No provenance attestation provenance

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

v3.3.3

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

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

1 finding

LOW No provenance attestation provenance

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

v3.2.9

1 finding

LOW No provenance attestation provenance

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

v3.2.8

1 finding

LOW No provenance attestation provenance

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

v3.2.7

1 finding

LOW No provenance attestation provenance

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

v3.2.6

1 finding

LOW No provenance attestation provenance

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

v3.2.5

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

1 finding

LOW No provenance attestation provenance

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

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

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.

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.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.

v2.1.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.

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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