Package Health/subscribo/dependencyresolver

subscribo/dependencyresolver

The MIT license, clear package structure, and lack of install-time scripts reduce adoption friction. Nearly ten years without repository activity leaves little evidence of ongoing maintenance or support.

Latest v0.1.1

Packagist

39%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in November 2016, with no releases in the last 12 months. This is strong evidence of an unmaintained package despite the absence of registry deprecation.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, consistent with the package's nearly ten-year release gap.

Repo popularity

The repository has zero stars and forks and only two watchers, providing little external evidence of adoption or review. Popularity is supporting evidence, so this reinforces rather than determines the assessment.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, though it is less important than the long inactivity period.

Security policy

The repository has no security policy, leaving no documented route for reporting vulnerabilities. This matters more for a package with no recent maintenance evidence.