daverandom/libdns

The stable API, narrow dependency set, repository tests, and release notes support predictable use. Maintenance has gone quiet, and the repository has no security policy or scanning tools, so pin this version and plan a reassessment before upgrading.

Latest v2.1.0

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 14 releases over more than 12 years, but there have been no releases in the last two years since April 2024. That established history helps, yet the prolonged release gap lowers confidence in continued maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the longer release gap. This is meaningful evidence of currently inactive maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while five issues and four pull requests remain open. The limited recent activity suggests unresolved maintenance demand.

Repo tooling

Composer is used for the build, showing basic project tooling, but no security scanning tools are configured. The missing scanning is a hygiene concern rather than evidence that the release is unsafe.

Security policy

The repository has no published security policy. That weakens vulnerability-reporting transparency for a DNS protocol library, with no provided compensating security process.