@metamask/design-system-tailwind-preset
Design System Tailwind CSS preset for MetaMask projects
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): MetaMask org migrated publishing to GitHub Actions CI with SLSA attestation; stable pattern for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 0 / 9 | |
| 0.9.0 | 0 / 9 | |
| 0.8.0 | 0 / 9 | |
| 0.7.0 | 0 / 9 | |
| 0.6.1 | 0 / 9 | |
| 0.6.0 | 0 / 9 | |
| 0.5.0 | 0 / 9 | |
| 0.4.0 | 0 / 9 | |
| 0.3.0 | 0 / 9 | |
| 0.2.0 | 0 / 9 | |
| 0.1.0 | 0 / 9 |
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-30. 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.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.