← Home

@canonical/terrazzo-lsp

npm Repository Homepage
20
Versions
—
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

ilayda21frankbanhuwshimianthonydillonsteverydzamylily1011bartazjpmartinsptpetesfrenchjmuzinamtrujedlerdabehniacanonical-organizationedisile-canonicalsteciuk-canonicalad.vlengr-aliando.gqninfa_jeonndv99goulin-canonicalimmortalcodesalvaromateoonibenjo-canonical

Keywords

design-tokenscss-custom-propertieslanguage-serverlspcanonicaldtcgvscode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Move to GitHub Actions CI publishing for Canonical org package, not a suspicious takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with CI automation transition, no other malicious indicators. ai
provenance no-provenance AI (provenance): Canonical org package; lack of Sigstore provenance is common and not a risk signal here. ai

Versions (showing 20 of 20)

Version Deps Published
0.8.1 4 / 4
0.6.1 4 / 4
0.6.0 4 / 4
0.5.2 4 / 4
0.5.1 4 / 4
0.5.0 4 / 4
0.4.5 4 / 4
0.4.4 4 / 4
0.4.3 4 / 4
0.4.2 4 / 4
0.4.1 4 / 4
0.4.0 4 / 4
0.3.3 4 / 4
0.3.2 4 / 4
0.3.1 4 / 4
0.3.0 4 / 4
0.2.0 4 / 4
0.1.0 2 / 4
0.0.2 1 / 4
0.0.1 1 / 4

v0.8.1

2 findings
HIGH Publisher changed: ad.vl → GitHub Actions (on 2026-07-19) provenance

This version was published by a different npm account than previous versions on 2026-07-19. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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