@mekari/pixel-textarea
Mekari Pixel | The textarea component allows you to easily create multi line text inputs 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Same-org internal dependency within the Mekari Pixel design system; stable pattern across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Mekari org publishes consistently without provenance; stable pattern across all pixel-* packages. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.3.37 | 2 / 2 | |
| 0.3.36 | 2 / 2 | |
| 0.3.35 | 2 / 2 | |
| 0.3.34 | 2 / 2 | |
| 0.3.33 | 2 / 2 |
v0.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.