@remotion/tailwind-v4
Enable TailwindCSS support in Remotion (TailwindCSS v4)
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 | AI (phantom-deps): PostCSS is a config-referenced dependency for this Tailwind integration; stable pattern. | ai | |
| phantom-deps | phantom-dep:postcss-preset-env | AI (phantom-deps): Config-referenced PostCSS plugin; expected for Tailwind integration packages. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/postcss | AI (phantom-deps): Core Tailwind v4 dependency referenced in config; stable for this package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): tailwindcss is a declared runtime dependency used via config/plugin integration, not direct import; stable FP for this package. | ai |
Versions (showing 51 of 171)
| Version | Deps | Published |
|---|---|---|
| 4.0.473 | 4 / 4 | |
| 4.0.472 | 4 / 4 | |
| 4.0.471 | 4 / 4 | |
| 4.0.470 | 4 / 4 | |
| 4.0.469 | 4 / 4 | |
| 4.0.468 | 4 / 4 | |
| 4.0.467 | 4 / 4 | |
| 4.0.466 | 3 / 4 | |
| 4.0.465 | 3 / 4 | |
| 4.0.464 | 3 / 4 | |
| 4.0.463 | 3 / 4 | |
| 4.0.462 | 3 / 4 | |
| 4.0.461 | 3 / 4 | |
| 4.0.460 | 3 / 4 | |
| 4.0.459 | 3 / 4 | |
| 4.0.458 | 3 / 4 | |
| 4.0.457 | 3 / 4 | |
| 4.0.456 | 3 / 4 | |
| 4.0.455 | 3 / 4 | |
| 4.0.454 | 3 / 4 | |
| 4.0.453 | 3 / 4 | |
| 4.0.452 | 3 / 4 | |
| 4.0.451 | 3 / 4 | |
| 4.0.450 | 3 / 4 | |
| 4.0.449 | 3 / 4 | |
| 4.0.448 | 3 / 4 | |
| 4.0.447 | 3 / 4 | |
| 4.0.446 | 3 / 4 | |
| 4.0.445 | 3 / 4 | |
| 4.0.444 | 3 / 4 | |
| 4.0.443 | 3 / 4 | |
| 4.0.442 | 3 / 4 | |
| 4.0.441 | 3 / 4 | |
| 4.0.440 | 3 / 4 | |
| 4.0.439 | 3 / 4 | |
| 4.0.438 | 4 / 4 | |
| 4.0.437 | 4 / 4 | |
| 4.0.436 | 4 / 4 | |
| 4.0.435 | 4 / 4 | |
| 4.0.434 | 4 / 4 | |
| 4.0.433 | 4 / 4 | |
| 4.0.432 | 4 / 4 | |
| 4.0.431 | 4 / 4 | |
| 4.0.430 | 4 / 4 | |
| 4.0.429 | 7 / 4 | |
| 4.0.428 | 7 / 4 | |
| 4.0.427 | 7 / 4 | |
| 4.0.426 | 7 / 4 | |
| 4.0.425 | 7 / 4 | |
| 4.0.424 | 7 / 4 | |
| 4.0.423 | 7 / 3 |
v4.0.473
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.472
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.471
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.470
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.469
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.468
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.467
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.466
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.465
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.464
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.463
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.462
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.461
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.460
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.459
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.458
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.457
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.456
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.455
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.454
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.441
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.440
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.439
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.438
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.437
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.436
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.435
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.434
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.433
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.432
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.431
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.430
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.429
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.428
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.427
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.426
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.425
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.424
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.423
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.