johnroyer/url-normalizer

The README, tests, MIT license, and release notes make the package straightforward to evaluate and integrate. Its tiny user base, missing security policy, and unpinned workflow actions leave less assurance around long-term maintenance and build hygiene.

Latest 2.1.1

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was over two years ago, and there were no releases in the last 12 months. That is a meaningful sign of slowing maintenance, although the repository was pushed more recently.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long release gap, this raises abandonment risk even though the repository is not archived.

Repo popularity

The repository has one star, no forks, and no watchers. Low popularity is not disqualifying for a small utility, but it provides little external evidence of community use or review.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest build-hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting and handling vulnerabilities.