libeo/category-tree

Release historydanger

Only two releases were published, both on February 19, 2024, with no release in the following two years and seven months. That is strong evidence of stalled maintenance for a package consumers may need to keep compatible.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the repository's relationship to this release is unclear rather than merely a normal subpackage naming difference.

Security policycaution

The repository has no security policy, which is a transparency and maintenance-process gap, though it is less significant than the stalled activity and unclear package-repository relationship.