@codaco/tailwind-config
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; legitimate pipeline migration for this org. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/nunito | AI (phantom-deps): Font package referenced in CSS config files, not JS imports; phantom detection is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@fontsource-variable/inclusive-sans | AI (phantom-deps): Font package referenced in CSS config files, not JS imports; phantom detection is a stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.5.0 | 3 / 2 | |
| 0.4.1 | 3 / 2 | |
| 0.4.0 | 3 / 2 | |
| 0.3.0 | 3 / 2 | |
| 0.2.0 | 3 / 2 |
v1.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-06-11. 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.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-10. 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.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.