← Home

remove-bom-stream

npm Repository Homepage

Remove a UTF8 BOM at the start of the stream.

4
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

yocontraphated

Keywords

bomremoveutf8streamingstream

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): yocontra (Conrad Pankoff) is a known Gulp core contributor; addition is a legitimate team expansion, not a suspicious takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by modernization (through2→streamx) is consistent with the Gulp ecosystem's known migration effort; not indicative of account takeover. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.0 1 / 8
1.2.0 3 / 11
1.1.0 3 / 11
1.0.0 3 / 11

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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