event-stream MIT 80 versions

event-stream

npm Repository Homepage

construct pipes of streams of events

80

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

right9ctrl

Keywords

streammapflatmapfiltersplitjoinmergereplace

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is used for protocol selection (http/https) based on user-supplied opts — a legitimate and stable pattern in this package.	ai	2026/04/22
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance by many years; no provenance is expected and stable for this package.	ai	2026/04/22
source-diff	encoded-string-file:test/replace.asynct.js	AI (source-diff): The 'encoded strings' are FizzBuzz test fixture data (human-readable compact representation of FizzBuzz output) in a test file, not obfuscated payloads. Stable false positive for this package.	ai	2026/04/22
publish-pattern	new-deps-added	AI (publish-pattern): optimist is a well-known CLI arg parsing library by the same author; its addition is consistent with legitimate feature development.	ai	2026/04/22
dependencies	unvetted-dep:stream-combiner	AI (dependencies): stream-combiner is a long-standing legitimate utility package; unvetted status is a registry gap, not a real risk signal for this package.	ai	2026/04/21
dependencies	unvetted-dep:map-stream	AI (dependencies): map-stream is a long-standing legitimate utility package by Dominic Tarr; unvetted status is a registry gap, not a real risk signal for this package.	ai	2026/04/21
dependencies	unvetted-dep:from	AI (dependencies): from is a long-standing legitimate utility package by Dominic Tarr; unvetted status is a registry gap, not a real risk signal for this package.	ai	2026/04/21

Versions (showing 80 of 80)

Version	Deps	Published
4.0.0	7 / 5	2018-09-16
3.3.4	7 / 5	2016-07-17
3.3.3	7 / 5	2016-06-18
3.3.2	7 / 5	2015-10-16
3.3.1	7 / 5	2015-05-06
3.3.0	7 / 5	2015-03-06
3.2.2	7 / 5	2015-02-02
3.2.1	7 / 5	2014-12-29
3.2.0	7 / 5	2014-12-27
3.1.7	7 / 5	2014-07-21
3.1.5	7 / 5	2014-04-30
3.1.4	7 / 5	2014-04-28
3.1.2	7 / 5	2014-04-13
3.1.1	7 / 5	2014-03-27
3.1.0	7 / 5	2014-01-09
3.0.20	7 / 5	2013-12-11
3.0.18	7 / 5	2013-12-04
3.0.17	7 / 5	2013-12-04
3.0.16	7 / 5	2013-07-13
3.0.15	7 / 5	2013-06-18
3.0.14	7 / 5	2013-04-22
3.0.13	7 / 5	2013-03-27
3.0.12	7 / 5	2013-03-09
3.0.11	7 / 5	2013-01-06
3.0.10	7 / 4	2012-12-13
3.0.9	7 / 4	2012-12-12
3.0.8	7 / 4	2012-11-27
3.0.7	7 / 4	2012-09-30
3.0.6	7 / 4	2012-09-30
3.0.5	7 / 4	2012-09-25
3.0.4	7 / 4	2012-08-31
3.0.3	7 / 4	2012-08-30
3.0.2	6 / 4	2012-08-19
3.0.1	6 / 4	2012-08-18
3.0.0	6 / 4	2012-08-18
2.2.3	5 / 4	2012-08-18
2.2.2	4 / 4	2012-08-15
2.2.1	4 / 4	2012-08-10
2.2.0	3 / 4	2012-08-07
2.1.9	3 / 4	2012-08-04
2.1.8	3 / 4	2012-07-23
2.1.7	3 / 4	2012-07-19
2.1.5	3 / 4	2012-07-11
2.1.4	3 / 4	2012-07-04
2.1.3	3 / 4	2012-07-04
2.1.2	1 / 4	2012-06-30
2.1.0	1 / 3	2012-06-26
2.0.10	1 / 3	2012-06-26
2.0.9	1 / 3	2012-06-26
2.0.4	1 / 3	2012-06-14
2.0.3	1 / 3	2012-06-12
2.0.2	1 / 3	2012-06-12
2.0.1	1 / 3	2012-06-12
2.0.0	1 / 3	2012-06-05
1.3.1	1 / 3	2012-06-05
1.3.0	1 / 3	2012-05-27
1.2.0	1 / 3	2012-05-25
1.1.0	1 / 3	2012-05-21
1.0.0	1 / 3	2012-05-21
0.10.0	1 / 3	2012-05-17
0.9.8	1 / 3	2012-05-03
0.9.7	1 / 3	2012-04-25
0.9.6	1 / 3	2012-04-25
0.9.4	1 / 3	2012-04-25
0.9.3	1 / 3	2012-04-25
0.9.2	1 / 3	2012-04-21
0.9.0	1 / 3	2012-04-21
0.8.2	1 / 3	2012-04-07
0.8.0	1 / 3	2012-03-25
0.7.0	1 / 3	2011-12-07
0.6.0	1 / 3	2011-11-07
0.5.3	1 / 3	2011-11-01
0.5.2	1 / 3	2011-11-01
0.5.1	1 / 3	2011-12-07
0.5.0	0 / 3	2011-12-07
0.4.0	0 / 3	2011-12-07
0.3.0	0 / 3	2011-12-07
0.2.1	0 / 3	2011-12-07
0.2.0	0 / 0	2011-12-07
0.1.0	0 / 0	2011-12-07

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.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.9

1 finding

LOW No provenance attestation provenance

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

v2.1.8

1 finding

LOW No provenance attestation provenance

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

v2.1.7

1 finding

LOW No provenance attestation provenance

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

v2.1.5

1 finding

LOW No provenance attestation provenance

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

v2.1.4

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

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.10

1 finding

LOW No provenance attestation provenance

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

v2.0.9

1 finding

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.

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.8

1 finding

LOW No provenance attestation provenance

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

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.4

1 finding

LOW No provenance attestation provenance

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

v0.9.3

1 finding

LOW No provenance attestation provenance

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

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

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

v0.6.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.

v0.5.3

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.

v0.5.2

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.

v0.5.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.

v0.5.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.

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

v0.3.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.

v0.2.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.

v0.2.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.

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