@nuxtjs/tailwindcss
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a declared runtime dep used via config references, not a direct import — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:autoprefixer | AI (phantom-deps): autoprefixer is a declared runtime dep used via config references — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:postcss-nesting | AI (phantom-deps): postcss-nesting is a declared runtime dep used via config references — stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 6.14.0 | 16 / 15 | |
| 6.13.2 | 13 / 16 | |
| 6.13.1 | 14 / 15 | |
| 6.13.0 | 14 / 15 | |
| 6.12.2 | 13 / 15 | |
| 6.12.1 | 12 / 15 |
v6.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.