replacestream BSD-3-Clause 13 versions

replacestream

npm Repository Homepage

A node.js through stream that does basic streaming text search and replace and is chunk boundary friendly

13

Versions

BSD-3-Clause

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

shinnnmehtaphysicaleugeneware

Keywords

replacetextregexstreamstreamsstreamingsearch

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:readable-stream	AI (dependencies): readable-stream is a well-known, widely-used Node.js core stream polyfill with a strong ecosystem track record; not a meaningful risk for this package.	ai	2026/04/21

Versions (showing 13 of 13)

Version	Deps	Published
0.3.0	1 / 2	2014-10-21
0.2.0	1 / 2	2014-09-11
0.1.4	1 / 2	2014-09-11
0.1.3	1 / 2	2014-02-27
0.1.2	1 / 2	2014-02-27
0.1.1	1 / 2	2014-02-27
0.1.0	1 / 2	2014-02-27
0.0.6	1 / 2	2013-09-07
0.0.5	1 / 2	2013-09-07
0.0.4	1 / 2	2013-09-07
0.0.3	1 / 2	2013-07-19
0.0.2	1 / 2	2013-07-08
0.0.1	1 / 2	2013-06-15

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

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