← Home

@canonical/token-types

npm Repository Homepage
16
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-tokenstypescriptcanonicaldtcg

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Manual account to GitHub Actions CI publisher is a provenance improvement, not compromise. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with CI/CD publishing transition, no new suspicious maintainer added. ai
provenance missing-githead AI (provenance): Established Canonical Webteam publisher with strong track record; likely CI environment change, not a supply-chain concern. ai

Versions (showing 16 of 16)

Version Deps Published
0.8.1 0 / 3
0.6.1 0 / 3
0.6.0 0 / 3
0.5.2 0 / 3
0.5.0 0 / 3
0.4.5 0 / 3
0.4.4 0 / 3
0.4.3 0 / 3
0.4.2 0 / 3
0.4.1 0 / 3
0.4.0 0 / 3
0.3.3 0 / 3
0.3.1 0 / 3
0.3.0 0 / 3
0.2.0 0 / 3
0.1.0 0 / 2

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.

LOW No provenance attestation provenance

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