dbeurive/tree

Release historydanger

The latest release was published in July 2016, and there have been no releases in nearly 10 years. This is strong evidence of abandonment risk despite the package having five historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.

Maintainerscaution

Only one registry maintainer is listed, which creates a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, providing little community backing or independent adoption evidence. Popularity is supporting evidence, but this reinforces the maintenance concern.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it is less severe than the lack of recent development.