ip2location/ip2proxy-php

The project has a clear owner, tests, documentation, licensing, and a release published alongside a recent repository update. Its slow release pace, no commits in the last three months, and absent security tooling leave maintenance and security coverage thinner than ideal.

Latest 4.3.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 9 years and has 13 releases, but only one release in the last 12 months with a median interval of about 237 days indicates a slow maintenance cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. The same-day release and repository push partly offset this, but recent ongoing maintenance capacity remains unclear.

Repo issue activity

There are no open issues or pull requests, and no issue or pull-request activity in the last month. This is orderly but provides little evidence of an active maintenance community.

Repo tooling

Composer is used for builds, but no security-scanning tools were detected, leaving automated security coverage weaker than ideal.

Security policy

The repository has no security policy, so there is no documented path for reporting vulnerabilities or explaining security response practices.