react-textarea-autosize
textarea component for React which grows with content
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher is a dedicated release bot (react-textarea-autosize-release-bot) with 30 approved versions; standard CI/CD automation by the existing maintainer team. | ai | |
| source-diff | obfuscated-file:dist/declarations/src/index.d.ts | AI (source-diff): TypeScript declaration file listing all textarea HTML/ARIA props in a Pick<> type — long lines are inherent to TS declarations, not obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Release bot account with long track record (2161 days, 30 approved versions); standard automated publishing setup. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of inactive maintainers (jdalton, kylemathews) during project modernization; original author and primary contributor remain. | ai |
Versions (showing 98 of 98)
| Version | Deps | Published |
|---|---|---|
| 8.5.9 | 3 / 33 | |
| 8.5.8 | 3 / 33 | |
| 8.5.7 | 3 / 33 | |
| 8.5.6 | 3 / 33 | |
| 8.5.5 | 3 / 33 | |
| 8.5.4 | 3 / 33 | |
| 8.5.3 | 3 / 33 | |
| 8.5.2 | 3 / 33 | |
| 8.5.1 | 3 / 33 | |
| 8.5.0 | 3 / 33 | |
| 8.4.1 | 3 / 33 | |
| 8.4.0 | 3 / 32 | |
| 8.3.4 | 3 / 32 | |
| 8.3.3 | 3 / 32 | |
| 8.3.2 | 3 / 32 | |
| 8.3.1 | 3 / 32 | |
| 8.3.0 | 3 / 31 | |
| 8.2.0 | 3 / 31 | |
| 8.1.1 | 3 / 31 | |
| 8.1.0 | 3 / 31 | |
| 8.0.1 | 3 / 30 | |
| 8.0.0 | 3 / 29 | |
| 7.1.2 | 2 / 34 | |
| 7.1.1 | 2 / 34 | |
| 7.1.0 | 2 / 34 | |
| 7.0.4 | 1 / 28 | |
| 7.0.3 | 1 / 28 | |
| 7.0.2 | 1 / 28 | |
| 7.0.1 | 1 / 28 | |
| 7.0.0 | 1 / 28 | |
| 6.1.0 | 1 / 21 | |
| 6.0.3 | 1 / 21 | |
| 6.0.2 | 1 / 21 | |
| 6.0.1 | 1 / 21 | |
| 6.0.0 | 1 / 21 | |
| 5.2.1 | 1 / 22 | |
| 5.2.0 | 1 / 22 | |
| 5.1.0 | 1 / 22 | |
| 5.0.7 | 1 / 21 | |
| 5.0.6 | 1 / 21 | |
| 5.0.5 | 1 / 21 | |
| 5.0.4 | 1 / 21 | |
| 5.0.3 | 1 / 21 | |
| 5.0.2 | 1 / 21 | |
| 5.0.1 | 1 / 18 | |
| 5.0.0 | 1 / 18 | |
| 4.3.2 | 1 / 18 | |
| 4.3.1 | 1 / 18 | |
| 4.3.0 | 1 / 18 | |
| 4.2.2 | 1 / 11 | |
| 4.2.1 | 1 / 11 | |
| 4.2.0 | 1 / 11 | |
| 4.1.0 | 1 / 10 | |
| 4.0.5 | 0 / 10 | |
| 4.0.4 | 0 / 5 | |
| 4.0.3 | 0 / 5 | |
| 4.0.2 | 0 / 5 | |
| 4.0.1 | 0 / 5 | |
| 4.0.0 | 0 / 5 | |
| 3.3.1 | 0 / 5 | |
| 3.3.0 | 0 / 5 | |
| 3.2.0 | 0 / 5 | |
| 3.1.0 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.5.4 | 0 / 4 | |
| 2.5.3 | 0 / 4 | |
| 2.5.2 | 0 / 4 | |
| 2.5.1 | 0 / 4 | |
| 2.5.0 | 0 / 4 | |
| 2.4.2 | 0 / 4 | |
| 2.4.1 | 0 / 4 | |
| 2.4.0 | 0 / 4 | |
| 2.3.1 | 0 / 4 | |
| 2.3.0 | 0 / 4 | |
| 2.2.3 | 0 / 4 | |
| 2.2.2 | 0 / 4 | |
| 2.2.1 | 0 / 4 | |
| 2.2.0 | 0 / 4 | |
| 2.1.3 | 0 / 4 | |
| 2.1.2 | 0 / 4 | |
| 2.1.1 | 0 / 4 | |
| 2.1.0 | 0 / 4 | |
| 2.0.1 | 0 / 4 | |
| 2.0.0 | 1 / 4 | |
| 1.1.0 | 1 / 1 | |
| 1.0.6 | 1 / 1 | |
| 1.0.5 | 1 / 1 | |
| 1.0.4 | 1 / 1 | |
| 1.0.3 | 1 / 2 | |
| 1.0.2 | 1 / 2 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 | |
| 0.3.1 | 1 / 2 | |
| 0.3.0 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.2 | 1 / 2 | |
| 0.1.1 | 1 / 2 | |
| 0.1.0 | 1 / 2 |
v8.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
3 findingsThis version was published by a different npm account than previous versions on 2020-05-23. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.