@versini/ui-toggle
[](https://www.npmjs.com/package/@versini/ui-toggle)  relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): tailwindcss is a declared runtime dep used via CSS/config, not direct JS import; stable false positive for this UI package. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 3 / 1 | |
| 7.0.3 | 3 / 1 | |
| 7.0.2 | 3 / 1 | |
| 7.0.1 | 3 / 1 | |
| 7.0.0 | 3 / 1 | |
| 6.3.0 | 3 / 1 | |
| 6.2.3 | 3 / 1 | |
| 6.2.2 | 3 / 1 | |
| 6.2.1 | 3 / 1 | |
| 6.2.0 | 3 / 1 | |
| 6.1.3 | 4 / 1 | |
| 6.1.2 | 4 / 1 | |
| 6.1.1 | 4 / 1 | |
| 6.1.0 | 4 / 1 | |
| 6.0.1 | 4 / 1 | |
| 6.0.0 | 4 / 1 | |
| 5.5.9 | 4 / 1 | |
| 5.5.8 | 4 / 1 | |
| 5.5.7 | 4 / 1 | |
| 5.5.6 | 4 / 1 | |
| 5.5.5 | 4 / 1 | |
| 5.5.4 | 4 / 1 | |
| 5.5.3 | 4 / 1 | |
| 5.5.2 | 4 / 1 | |
| 5.5.1 | 4 / 1 | |
| 5.5.0 | 4 / 1 | |
| 5.4.0 | 4 / 1 | |
| 5.3.0 | 4 / 1 |
v8.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.