← Home

@herb-tools/highlighter

Syntax highlighter and diagnostic renderer for HTML+ERB templates.

35
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

marcoroth

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/herb-highlight.js AI (source-diff): Base64 string is an inline WASM binary (AGFzbQ = \0asm magic bytes) from Emscripten compilation. Standard pattern for native-code-to-WASM packages. ai
provenance no-provenance AI (provenance): Established herb-tools ecosystem package with 34 versions and 145k weekly downloads; lack of Sigstore provenance is common and not a meaningful risk signal here. ai

Versions (showing 35 of 35)

Version Deps Published
0.10.2 2 / 0
0.10.1 2 / 0
0.10.0 2 / 0
0.9.7 2 / 0
0.9.6 2 / 0
0.9.5 2 / 0
0.9.4 2 / 0
0.9.3 2 / 0
0.9.2 2 / 0
0.9.1 2 / 0
0.9.0 2 / 0
0.8.10 2 / 0
0.8.9 2 / 0
0.8.8 2 / 0
0.8.7 2 / 0
0.8.6 2 / 0
0.8.5 2 / 0
0.8.4 2 / 0
0.8.3 2 / 0
0.8.2 2 / 0
0.8.1 2 / 0
0.8.0 2 / 0
0.7.5 3 / 0
0.7.4 3 / 0
0.7.3 3 / 0
0.7.2 3 / 0
0.7.1 3 / 0
0.7.0 3 / 0
0.6.1 4 / 6
0.6.0 4 / 6
0.5.0 4 / 6
0.4.3 4 / 6
0.4.2 4 / 6
0.4.1 4 / 6
0.4.0 4 / 6

v0.10.2

1 finding
INFO No provenance attestation provenance

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