maxicms/ua-parser

A clear MIT license, substantial README, and broad test suite make the package understandable and workable. However, it has had no release or commit activity for over nine years, and the linked repository does not identify or mention this package. Pinning this version carries substantial maintenance and ownership uncertainty.

Latest 0.2.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both dating from June 2017, with no release in over nine years. That strongly raises abandonment risk for a library whose parsing data and compatibility may age.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Together with the last push in 2017, this is strong evidence that active maintenance has stopped.

Repo package mention

The repository name does not match the package name and its README does not mention the package, leaving ownership and provenance unclear even though a repository was linked.

Repo popularity

The repository has one star, zero forks, and one watcher, providing little supporting evidence of a maintained user or contributor community. Low popularity alone is not decisive for a small library.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. This is a modest hygiene gap rather than proof of unsafe code.