← Home

stream-handlebars

npm Repository Homepage

Extends handlebars with a streaming interface for .compile()

8
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

75lb

Keywords

handlebarsstreamcompile

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:handlebars AI (dependencies): Handlebars is the core dependency this package is built around; its use is expected and legitimate for stream-handlebars across all versions. ai
provenance no-provenance AI (provenance): Established package (4058 days old) published before Sigstore provenance was available; absence is expected and not a security risk for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Publisher 75lb has a strong track record (1383 approved, 0 rejected). The release is a minor update with only a lint script removal; no suspicious changes indicative of account takeover. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.0 2 / 2
0.1.6 2 / 2
0.1.5 2 / 2
0.1.4 2 / 2
0.1.3 2 / 2
0.1.2 2 / 1
0.1.1 1 / 1
0.1.0 1 / 1

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

1 finding
LOW No provenance attestation provenance

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

v0.1.5

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

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