chieftools/dns-resolver

This is a usable but relatively young package with clear licensing, a matching organization-backed repository, active release publishing, repository tests, security documentation, Dependabot, and no deprecation or dangerous workflow findings. However, it has only 153 days of history, releases are unusually clustered, repository commit activity shows no commits or active maintainers in the last 3 months, repository popularity is minimal, and the CI workflow does not declare top-level token permissions. The repository evidence partly offsets the artifact's missing tests and changelog, but the limited demonstrated maintenance history warrants caution before adopting it as a critical dependency.

Latest v1.2.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Fourteen releases over 153 days show active publishing, but the median release interval is about 50 minutes, indicating an unusually clustered and still-maturing release history rather than long-established stability.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. Although the repository was recently pushed and releases are active, the absence of sustained commit activity is a meaningful maintenance concern for a young package.

Repo issue activity

There are no open issues and one open pull request, but no issues or pull requests were closed or merged in the last month. This offers limited evidence of active community maintenance.

Repo popularity

The repository has only 1 star, 1 fork, and 0 watchers. This provides little external adoption evidence, although low popularity alone is not a decisive health concern for a specialized package.

Token permissions

The only workflow lacks top-level token permissions. No write permissions were observed, but the absence of an explicit least-privilege declaration is a CI hygiene gap.