@terrazzo/cli
CLI for managing design tokens using the Design Tokens Community Group (DTCG) standard and generating code for any platform via plugins.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lab/assets/index-B8CS4Pk9.js | AI (source-diff): Vite-bundled browser asset for token-lab UI; minification is expected and content matches React/scheduler patterns. | ai | |
| phantom-deps | phantom-dep:dtcg-examples | AI (phantom-deps): dtcg-examples is a data/example package likely used at runtime via config, not direct import; stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; this is the expected CI/CD publishing pattern for this package. | ai | |
| source-diff | obfuscated-file:dist/lab/assets/index-vpFefk-2.js | AI (source-diff): Standard Vite-bundled minified frontend asset for the token lab UI; not malicious obfuscation. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @terrazzo/cli is a well-known design-token CLI with no relation to joi; Levenshtein match is a false positive that will recur on every version. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): The fetch in lab.tsx targets a relative URL /api/tokens in a React browser UI component for the CLI's local dev server — not telemetry or exfiltration. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 18 / 5 | |
| 2.1.0 | 19 / 5 | |
| 2.0.3 | 19 / 5 | |
| 2.0.2 | 19 / 5 | |
| 2.0.1 | 19 / 5 | |
| 2.0.0 | 19 / 5 | |
| 0.10.5 | 15 / 3 |
v2.2.0
3 findingsThis version was published by a different npm account than previous versions on 2026-05-16. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.