rc-tree-select
tree-select ui component for react
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is declared in dependencies and used in compiled output; false positive from config-only detection. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yiminghe is a known react-component org contributor; addition is consistent with legitimate team expansion in this well-established package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (classnames, object-assign, rc-animate, rc-util) are all well-known, legitimate React ecosystem packages with no malicious signals. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is consistent with early-stage feature development adding animation, utility, and CSS class management support. No obfuscation or injected payload indicators. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; absence is expected and not a risk signal for this established package. | ai | |
| dependencies | unvetted-dep:rc-animate | AI (dependencies): rc-animate is a sibling react-component ecosystem package widely used across rc-* components; not a meaningful risk for this package. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 5.26.0 | 5 / 31 | |
| 5.24.5 | 5 / 31 | |
| 5.24.3 | 5 / 31 | |
| 5.24.2 | 5 / 31 | |
| 5.24.1 | 5 / 31 | |
| 5.24.0 | 5 / 31 | |
| 5.23.0 | 5 / 29 | |
| 5.22.2 | 5 / 29 | |
| 5.22.1 | 5 / 28 | |
| 5.22.0 | 5 / 28 | |
| 5.21.0 | 5 / 28 | |
| 5.20.0 | 5 / 28 | |
| 5.19.0 | 5 / 28 | |
| 5.18.0 | 5 / 28 | |
| 5.17.0 | 5 / 28 | |
| 5.15.0 | 5 / 24 | |
| 5.14.1 | 5 / 24 | |
| 5.13.0 | 5 / 24 | |
| 5.12.1 | 5 / 24 | |
| 5.12.0 | 5 / 24 | |
| 5.11.2 | 5 / 24 | |
| 5.11.1 | 5 / 24 | |
| 5.11.0 | 5 / 24 | |
| 5.9.0 | 5 / 24 | |
| 5.7.0 | 5 / 24 | |
| 5.6.0 | 5 / 24 | |
| 5.5.5 | 5 / 24 | |
| 5.5.3 | 5 / 23 | |
| 5.5.2 | 5 / 23 | |
| 5.5.1 | 5 / 23 | |
| 5.4.1 | 5 / 20 | |
| 1.8.6 | 6 / 11 | |
| 1.8.5 | 6 / 11 | |
| 1.8.4 | 6 / 11 | |
| 1.8.2 | 6 / 11 | |
| 1.8.1 | 6 / 11 | |
| 1.8.0 | 6 / 11 | |
| 1.7.10 | 6 / 11 | |
| 1.7.9 | 6 / 12 | |
| 1.7.7 | 6 / 12 | |
| 1.7.6 | 6 / 12 | |
| 1.7.5 | 6 / 12 | |
| 1.7.3 | 6 / 12 | |
| 1.7.2 | 6 / 12 | |
| 1.7.0 | 6 / 11 | |
| 1.6.4 | 6 / 11 | |
| 1.6.3 | 6 / 11 | |
| 1.6.2 | 6 / 11 | |
| 1.6.0 | 6 / 11 | |
| 1.5.7 | 6 / 11 | |
| 1.5.6 | 6 / 11 |
v5.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.5
2 findingsThis version was published by a different npm account than previous versions on 2024-11-21. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (zombiej) than the most recent previously approved version (afc163) on 2024-09-03, but zombiej is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.