goober
A less than 1KB css-in-js solution
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tiny-css-prefixer | AI (phantom-deps): Author's own sibling package used for CSS prefixing; likely referenced indirectly in build, not malicious. | ai | |
| dependencies | unvetted-dep:tiny-css-prefixer | AI (dependencies): Small utility dep from same maintainer's monorepo, long-standing and stable. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 2.1.19 | 0 / 23 | |
| 2.1.18 | 0 / 23 | |
| 2.1.17 | 0 / 23 | |
| 2.1.16 | 0 / 23 | |
| 2.1.15 | 0 / 23 | |
| 2.1.14 | 0 / 23 | |
| 2.1.13 | 0 / 23 | |
| 2.1.12 | 0 / 23 | |
| 2.1.11 | 0 / 23 | |
| 2.1.10 | 0 / 23 | |
| 2.1.9 | 0 / 23 | |
| 2.1.8 | 0 / 23 | |
| 2.1.7 | 0 / 23 | |
| 2.1.6 | 0 / 23 | |
| 2.1.5 | 0 / 23 | |
| 2.1.4 | 0 / 23 | |
| 2.1.3 | 0 / 23 | |
| 2.1.2 | 0 / 23 | |
| 2.1.1 | 0 / 23 | |
| 2.1.0 | 0 / 23 | |
| 2.0.45 | 0 / 23 | |
| 2.0.44 | 0 / 22 | |
| 2.0.43 | 0 / 22 | |
| 2.0.42 | 0 / 22 | |
| 2.0.41 | 0 / 22 | |
| 2.0.40 | 0 / 22 | |
| 2.0.39 | 0 / 22 | |
| 2.0.38 | 0 / 22 | |
| 2.0.37 | 0 / 22 | |
| 2.0.36 | 0 / 22 | |
| 2.0.35 | 0 / 22 | |
| 2.0.34 | 0 / 22 | |
| 2.0.33 | 0 / 22 | |
| 2.0.32 | 0 / 22 | |
| 2.0.31 | 0 / 22 | |
| 2.0.30 | 0 / 21 | |
| 2.0.29 | 0 / 21 | |
| 2.0.28 | 0 / 21 | |
| 2.0.27 | 0 / 21 | |
| 2.0.26 | 0 / 21 | |
| 2.0.25 | 0 / 21 | |
| 2.0.24 | 0 / 21 | |
| 2.0.23 | 0 / 21 | |
| 2.0.22 | 0 / 21 | |
| 2.0.21 | 0 / 21 | |
| 2.0.20 | 0 / 21 | |
| 2.0.19 | 0 / 21 | |
| 2.0.18 | 0 / 21 | |
| 2.0.17 | 0 / 21 | |
| 2.0.16 | 0 / 21 | |
| 2.0.15 | 0 / 21 | |
| 2.0.14 | 0 / 21 | |
| 2.0.13 | 0 / 21 | |
| 2.0.12 | 0 / 21 | |
| 2.0.11 | 0 / 21 | |
| 2.0.10 | 0 / 21 | |
| 2.0.9 | 0 / 21 | |
| 2.0.8 | 0 / 21 | |
| 2.0.7 | 0 / 21 | |
| 2.0.6 | 0 / 21 | |
| 2.0.5 | 0 / 21 | |
| 2.0.4 | 0 / 21 | |
| 2.0.3 | 0 / 21 | |
| 2.0.2 | 0 / 21 | |
| 2.0.1 | 0 / 21 | |
| 2.0.0 | 1 / 21 |
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.