@canonical/design-tokens
18
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-propertiescanonicaldtcg
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@canonical/terrazzo-lsp | AI (phantom-deps): Same-org sibling package, used via CLI not import. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-driven maintainer cleanup, no takeover indicators. | ai | |
| dependencies | unvetted-dep:@canonical/terrazzo-lsp | AI (dependencies): Same-org (@canonical) dep directly used as the terrazzo-lsp binary; consistent with package purpose. | ai | |
| provenance | no-provenance | AI (provenance): Canonical org package; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 1 / 7 | |
| 0.6.1 | 1 / 7 | |
| 0.6.0 | 1 / 7 | |
| 0.5.2 | 1 / 7 | |
| 0.5.0 | 1 / 7 | |
| 0.4.5 | 1 / 7 | |
| 0.4.4 | 1 / 7 | |
| 0.4.3 | 1 / 7 | |
| 0.4.2 | 1 / 7 | |
| 0.4.1 | 1 / 7 | |
| 0.4.0 | 1 / 7 | |
| 0.3.3 | 1 / 7 | |
| 0.3.1 | 1 / 7 | |
| 0.3.0 | 1 / 7 | |
| 0.2.0 | 1 / 7 | |
| 0.1.0 | 0 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 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.