@trackunit/css-tailwind
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): 451 days stale with no removal; consistent with legitimate publisher, not takeover. | ai | |
| phantom-deps | phantom-dep:@tailwindcss/typography | AI (phantom-deps): Used as Tailwind plugin in config, not directly imported. | ai | |
| phantom-deps | phantom-dep:@trackunit/css-component-tokens | AI (phantom-deps): Same-org design token dep referenced via config, not code import. | ai | |
| phantom-deps | phantom-dep:@trackunit/css-tailwind-custom-properties-plugin | AI (phantom-deps): Same-org Tailwind plugin dep used via config, not direct import. | ai |
Versions (showing 51 of 264)
| Version | Deps | Published |
|---|---|---|
| 1.11.33 | 6 / 0 | |
| 1.11.32 | 6 / 0 | |
| 1.11.31 | 6 / 0 | |
| 1.11.30 | 6 / 0 | |
| 1.11.29 | 6 / 0 | |
| 1.11.28 | 6 / 0 | |
| 1.11.27 | 6 / 0 | |
| 1.11.26 | 6 / 0 | |
| 1.11.25 | 6 / 0 | |
| 1.11.24 | 6 / 0 | |
| 1.11.23 | 6 / 0 | |
| 1.11.22 | 6 / 0 | |
| 1.11.21 | 6 / 0 | |
| 1.11.20 | 6 / 0 | |
| 1.11.19 | 6 / 0 | |
| 1.11.17 | 6 / 0 | |
| 1.11.16 | 6 / 0 | |
| 1.11.15 | 6 / 0 | |
| 1.11.14 | 6 / 0 | |
| 1.11.13 | 6 / 0 | |
| 1.11.12 | 6 / 0 | |
| 1.11.11 | 6 / 0 | |
| 1.11.10 | 6 / 0 | |
| 1.11.9 | 6 / 0 | |
| 1.11.8 | 6 / 0 | |
| 1.11.7 | 6 / 0 | |
| 1.11.0 | 6 / 0 | |
| 1.10.27 | 6 / 0 | |
| 1.10.26 | 6 / 0 | |
| 1.10.24 | 6 / 0 | |
| 1.10.23 | 6 / 0 | |
| 1.10.22 | 6 / 0 | |
| 1.10.18 | 6 / 0 | |
| 1.10.16 | 6 / 0 | |
| 1.10.15 | 6 / 0 | |
| 1.10.14 | 6 / 0 | |
| 1.10.13 | 6 / 0 | |
| 1.10.12 | 6 / 0 | |
| 1.10.11 | 6 / 0 | |
| 1.10.10 | 6 / 0 | |
| 1.10.9 | 6 / 0 | |
| 1.10.5 | 6 / 0 | |
| 1.10.4 | 6 / 0 | |
| 1.10.3 | 6 / 0 | |
| 1.10.1 | 6 / 0 | |
| 1.10.0 | 6 / 0 | |
| 1.9.22 | 6 / 0 | |
| 1.9.21 | 6 / 0 | |
| 1.9.20 | 6 / 0 | |
| 1.9.16 | 6 / 0 | |
| 1.9.15 | 6 / 0 |
v1.11.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.