binbinly/tree-view

Release historydanger

Only two releases were published, both in June 2020, with no release in more than six years. That strongly indicates abandonment risk for a dependency.

Licensecaution

No declared license, license file, or repository license file was detected. This creates a material legal and transparency problem for adoption.

Maintainerscaution

The package has one registry maintainer. A single maintainer is not disqualifying, but combined with the long release gap it provides little maintenance capacity.

Repository archivedcaution

The repository is not archived, which is a positive, but it was last pushed in June 2020 and shows no newer maintenance evidence.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a secondary concern alongside the stronger maintenance gaps.