← Home

@zenithbuild/language

npm Repository Homepage

Canonical Zenith syntax highlighting, snippets, and VS Code integration

9
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

judahsullivan

Keywords

zenithzensyntaxhighlightingintellisenseframework

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread in neovim smoke test script is a standard pattern for passing env to a child process; not a security risk. ai
provenance slsa-provenance AI (provenance): Package consistently published via CI/CD with Sigstore attestation; stable supply chain signal for this package. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used only in dev build script for marketplace packaging, not in runtime extension code. ai
dependencies unvetted-dep:vscode-languageclient AI (dependencies): vscode-languageclient is a standard Microsoft VS Code LSP client library; expected dependency for this type of package. ai

Versions (showing 9 of 9)

Version Deps Published
1.4.3 1 / 4
1.4.2 1 / 4
1.4.0 1 / 4
1.3.3 1 / 4
0.7.10 4 / 6
0.7.7 4 / 6
0.7.4 4 / 6
0.6.1 1 / 4
0.6.0 1 / 4

v1.4.3

1 finding
LOW No provenance attestation provenance

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

v1.4.2

1 finding
LOW No provenance attestation provenance

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

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

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.7.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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