ilya/resolver

Compatibility and security context are limited for a very old, minimally developed package. It is correctly licensed, has a matching repository, no install-time scripts, and a small dependency surface, but it should not be a new dependency without a maintained alternative.

Latest 1.1

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, with the latest published about 12 years ago and no releases in the last 12 months. The short seven-day release interval in 2014 does not compensate for the long subsequent inactivity.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project whose development stopped about 12 years ago.

Project backing

The repository is owned by an individual account rather than an organization, so there is no visible organizational backing to compensate for the thin maintenance history.

Repo popularity

The repository has only 2 stars and 1 fork, offering little evidence of broad community adoption or a strong support base.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security scanning tooling is present. This is a modest transparency and maintenance gap for an old package.