@aurodesignsystem/design-tokens
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs a local .mjs script for token generation; consistent with this package's documented design-token build workflow. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a runtime dependency used in CSS transformation scripts; heuristic false positive for this build-oriented package. | ai | |
| phantom-deps | phantom-dep:@aurodesignsystem/auro-tokendefinitions | AI (phantom-deps): Same-org token definitions package; used at runtime in postinstall/build scripts, not directly imported in JS modules. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.21.0 | 0 / 18 | |
| 8.20.0 | 0 / 18 | |
| 8.19.0 | 0 / 18 | |
| 8.18.0 | 0 / 18 | |
| 8.17.0 | 0 / 18 | |
| 8.7.0 | 3 / 10 | |
| 8.2.2 | 2 / 10 | |
| 8.2.1 | 2 / 10 | |
| 8.2.0 | 2 / 10 |
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.0
2 findingsScript: node packageScripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.2
2 findingsScript: node packageScripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.1
2 findingsScript: node packageScripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
2 findingsScript: node packageScripts/postinstall.mjs
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.