@fiscozen/textarea
Design System Textarea component
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal design system component; sparse metadata is expected for org-scoped packages not intended for public discovery. | ai | |
| phantom-deps | phantom-dep:@fiscozen/icons | AI (phantom-deps): Same org scope; likely used transitively or in built output rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@fiscozen/alert | AI (phantom-deps): Same-org dep declared as runtime dependency; likely re-exported rather than directly imported in source. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 1 / 18 | |
| 3.0.1 | 1 / 18 | |
| 3.0.0 | 1 / 18 | |
| 2.0.0 | 0 / 18 | |
| 1.0.0 | 0 / 18 | |
| 0.1.4 | 0 / 18 | |
| 0.1.3 | 1 / 18 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.