markbaker/quadtrees

The MIT license, small runtime dependency surface, and clear package-to-repository match support adoption. The project has had no registry releases or repository commits since 2019, leaving maintenance and compatibility risks.

Latest 2.2.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is consistent with a small user-owned project, but it leaves little visible publishing redundancy when combined with the long period of inactivity.

Release history

The package is about 7 years old but has had no releases in the last 12 months; its eight releases were concentrated in November 2018, which points to prolonged inactivity.

Repo commit activity

There were zero commits and zero active maintainers in the last 3 months, reinforcing that ongoing fixes and compatibility work are unlikely.

Repo issue activity

There was no issue or pull-request activity in the last month and one issue remains open, providing no evidence of active support.

Repo tooling

The repository uses Composer, but no security-scanning tool is present. This is a modest transparency and maintenance gap rather than evidence that the release is unsafe.