polidog/quick-dns

The small, single-person project has almost no sustained maintenance or security-process evidence. Its README, tests, simple dependency profile, and MIT declaration provide useful transparency, but they do not offset the long period without repository activity.

Latest 0.0.3

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 3 releases, with none in the last 12 months and a median interval of about 1,069 days; the latest registry release was in 2019. This is strong evidence of abandonment risk.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, consistent with the repository's last push being in 2013. This leaves current maintenance and compatibility issues unlikely to receive attention.

Maintainers

One registry maintainer account is listed, matching the user-owned repository rather than indicating organizational backing. The thin maintainer base increases continuity risk alongside the inactive repository.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher, providing little external evidence of adoption or community support. Popularity is supporting evidence only, so this reinforces rather than determines the maintenance concern.

Repo tooling

Composer is used as a build tool, but no security scanning tooling is present. That is a modest transparency and maintenance gap, though it is less important than the project's lack of recent activity.