@nativescript/tailwind
TailwindCSS for NativeScript
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss-preset-env | AI (phantom-deps): Declared as runtime dep; used in PostCSS config context, not directly imported in JS — stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@csstools/postcss-is-pseudo-class | AI (phantom-deps): Declared as runtime dep; PostCSS plugin used via config, not direct JS import — stable FP for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.8 | 5 / 3 | |
| 4.0.7 | 4 / 3 | |
| 4.0.6 | 4 / 3 | |
| 4.0.5 | 4 / 3 | |
| 4.0.4 | 4 / 3 |
v4.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.