@versini/ui-textarea
[](https://www.npmjs.com/package/@versini/ui-textarea)  relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; publisher has strong approval track record. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Tailwindcss is a build-time CSS dependency referenced in config; not imported directly in source. Stable pattern for this UI library. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 7.0.4 | 4 / 2 | |
| 7.0.3 | 4 / 2 | |
| 7.0.2 | 4 / 2 | |
| 7.0.1 | 4 / 2 | |
| 7.0.0 | 4 / 2 | |
| 6.3.4 | 4 / 2 | |
| 6.3.3 | 4 / 2 | |
| 6.3.2 | 4 / 2 | |
| 6.3.1 | 4 / 2 | |
| 6.3.0 | 4 / 2 | |
| 6.2.1 | 5 / 2 | |
| 6.2.0 | 5 / 2 | |
| 6.1.1 | 5 / 2 | |
| 6.1.0 | 5 / 2 | |
| 6.0.1 | 5 / 2 | |
| 6.0.0 | 5 / 2 | |
| 5.1.8 | 5 / 2 | |
| 5.1.7 | 5 / 2 | |
| 5.1.6 | 5 / 2 | |
| 5.1.5 | 5 / 2 | |
| 5.1.4 | 5 / 2 | |
| 5.1.3 | 5 / 2 | |
| 5.1.2 | 5 / 2 | |
| 5.1.1 | 5 / 2 | |
| 5.1.0 | 5 / 2 |
v7.0.4
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
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.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.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.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.