react-treebeard
React Tree View 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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The raw IP 0.0.0.0:8080 is in example/webpack.config.js as a standard webpack-dev-server client URL — a well-known dev tooling pattern, not a malicious network request. | ai | |
| provenance | publisher-changed | AI (provenance): ndelangen is a well-known Storybook maintainer with 14,170 approved packages and 0 rejected. The repo URL points to the storybooks org, confirming a legitimate org-level maintainer transition. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.2.4 | 5 / 28 | |
| 3.2.3 | 7 / 31 | |
| 3.2.2 | 7 / 31 | |
| 3.2.1 | 7 / 31 | |
| 3.2.0 | 7 / 43 | |
| 3.1.0 | 7 / 40 | |
| 2.1.0 | 6 / 40 | |
| 2.0.3 | 6 / 40 | |
| 2.0.2 | 6 / 41 | |
| 2.0.1 | 6 / 35 | |
| 2.0.0 | 6 / 35 | |
| 1.1.4 | 5 / 36 | |
| 1.1.3 | 6 / 36 | |
| 1.1.2 | 6 / 36 | |
| 1.1.1 | 6 / 36 | |
| 1.1.0 | 6 / 36 | |
| 1.0.14 | 4 / 36 | |
| 1.0.13 | 4 / 36 | |
| 1.0.12 | 4 / 36 | |
| 1.0.11 | 4 / 35 | |
| 1.0.10 | 4 / 35 | |
| 1.0.9 | 4 / 35 | |
| 1.0.7 | 6 / 33 | |
| 1.0.6 | 6 / 32 | |
| 1.0.5 | 6 / 32 | |
| 1.0.4 | 7 / 32 | |
| 1.0.3 | 7 / 32 | |
| 1.0.2 | 7 / 32 | |
| 1.0.1 | 6 / 33 | |
| 1.0.0 | 6 / 33 |
v3.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-11. This could indicate a legitimate maintainer transition or an account compromise.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-09-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-07-17. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.1
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.