Package Health/jeroendesloovere/geolocation-php-api

jeroendesloovere/geolocation-php-api

Usable with caveats: the package is clearly licensed, stable, tested, and tied to its own unarchived repository. However, it has had no registry release in over three years and no commits in the last three months, so maintenance appears limited.

Latest 2.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match the same individual account, providing direct ownership alignment. A single-person project can still be healthy, but it offers less organizational continuity than a backed project.

Release history

The package has 12 releases since 2013, but none in the last three years and none during the last 12 months. That materially reduces confidence that compatibility or security issues will receive timely fixes.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. This suggests limited current maintenance capacity and is the main ongoing-adoption concern.

Repo tooling

Composer is used as a build tool, but no security scanning tool is reported. For a small PHP library this is a transparency gap rather than evidence of an unsafe release.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This weakens security transparency, especially for a library that calls an external mapping API.