style-dictionary
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transitioned to GitHub Actions CI/CD publishing with SLSA provenance — this is a supply chain improvement, not a compromise signal. Stable for this package going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jorenbroekema is already listed as a contributor in package.json and is a known style-dictionary contributor. Addition is legitimate. | ai | |
| source-diff | encoded-string-file:lib/common/transforms.js | AI (source-diff): The base64 string is a JSDoc documentation example for the asset/base64 transform feature, decoding to a harmless .editorconfig file. This is expected and stable for this package. | ai | |
| source-diff | encoded-string-file:lib/common/transforms.d.ts | AI (source-diff): Same base64 documentation example mirrored in the TypeScript declaration file. Benign .editorconfig content used as a JSDoc return value example. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 5.4.2 | 13 / 44 | |
| 5.4.1 | 13 / 44 | |
| 5.4.0 | 13 / 44 | |
| 5.3.3 | 13 / 48 | |
| 5.3.2 | 13 / 48 | |
| 5.3.1 | 13 / 48 | |
| 5.3.0 | 13 / 48 | |
| 5.2.0 | 12 / 48 | |
| 5.1.4 | 12 / 48 | |
| 5.1.3 | 12 / 48 | |
| 5.1.1 | 12 / 48 | |
| 5.1.0 | 12 / 48 | |
| 5.0.4 | 12 / 48 | |
| 5.0.3 | 12 / 48 | |
| 3.9.2 | 9 / 22 | |
| 3.9.1 | 9 / 22 | |
| 3.9.0 | 9 / 22 | |
| 3.8.0 | 9 / 22 | |
| 3.7.2 | 9 / 22 | |
| 3.7.1 | 9 / 22 | |
| 3.7.0 | 9 / 22 | |
| 3.1.1 | 9 / 22 | |
| 3.1.0 | 8 / 23 | |
| 3.0.3 | 8 / 22 | |
| 3.0.2 | 8 / 22 | |
| 3.0.1 | 8 / 22 | |
| 3.0.0 | 8 / 22 | |
| 2.10.3 | 8 / 18 | |
| 2.10.2 | 8 / 18 | |
| 2.10.1 | 8 / 18 | |
| 2.10.0 | 8 / 18 | |
| 2.9.0 | 8 / 18 | |
| 2.8.3 | 8 / 18 | |
| 2.8.2 | 8 / 18 | |
| 2.8.1 | 8 / 17 | |
| 2.8.0 | 8 / 19 | |
| 2.7.0 | 8 / 14 | |
| 2.6.2 | 8 / 14 | |
| 2.6.1 | 8 / 14 | |
| 2.6.0 | 8 / 14 | |
| 2.5.0 | 8 / 14 | |
| 2.4.0 | 7 / 10 | |
| 2.3.0 | 7 / 10 | |
| 2.2.1 | 6 / 10 | |
| 2.2.0 | 6 / 10 | |
| 2.1.0 | 5 / 7 | |
| 2.0.0 | 5 / 4 |
v5.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.4
2 findingsThis version was published by a different npm account than previous versions on 2026-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-07. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.