ama-team/tree-access

Release historydanger

Only two releases were published, both in January 2018, with no releases in the last eight years. This is strong evidence of abandonment despite the package not being deprecated.

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 visible ongoing maintenance.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That weakens ongoing assurance, although it does not by itself indicate an unsafe release.

Security policycaution

The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency gap for a library intended to be embedded in applications.