@tokens-studio/tokenscript-interpreter
A TypeScript interpreter for TokenScript, a domain-specific language for design token manipulation and computation
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Internal team rotation within Tokens Studio org; new maintainer shares org namespace. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal paired with same-org addition; consistent with team handoff, not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is first-party @tokens-studio/schema-validation replacing zod; low risk. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Large files are source maps and compiled bundles consistent with major version bump. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present to elevate this. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.38.0 | 4 / 11 | |
| 0.37.1 | 4 / 11 | |
| 0.37.0 | 4 / 11 | |
| 0.36.4 | 4 / 11 | |
| 0.36.3 | 4 / 11 | |
| 0.36.2 | 4 / 11 | |
| 0.36.1 | 4 / 11 | |
| 0.36.0 | 4 / 11 | |
| 0.34.0 | 4 / 11 | |
| 0.33.0 | 4 / 11 | |
| 0.32.0 | 4 / 11 | |
| 0.5.8 | 4 / 11 | |
| 0.5.7 | 4 / 11 | |
| 0.5.6 | 4 / 11 | |
| 0.5.4 | 4 / 9 |
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.