carawebs/address

The README, license, and small dependency set make its intended use easy to understand. No automated security tooling is visible, so ongoing maintenance would need to be checked outside the package.

Latest 1.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in January 2017, with none in the past nine years. That long period without a new release is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the past three months. Combined with the repository's last push being about nine years ago, this indicates sustained inactivity.

Repo popularity

The repository has zero stars, one fork, and one watcher. Low adoption is supporting evidence of limited maturity, though popularity alone is not decisive.

Repo tooling

Composer is used for the build, which is appropriate for a Packagist package, but no security scanning tools are configured. The missing scanning is a minor transparency and maintenance gap.

Security policy

The repository has no security policy. For a small WordPress plugin this is a modest gap, but it leaves vulnerability reporting and response expectations undocumented.