danog/libdns-native

Tests, documentation, licensing, and a small dependency set support basic transparency and maintenance quality. The missing security policy leaves less guidance for handling vulnerabilities.

Latest 0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over seven years ago, with no releases in the last 12 months. That is strong evidence of a project that may no longer be maintained.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, with its last push in August 2019. This materially increases abandonment risk.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. The missing scanner is a hygiene gap, not evidence that the release is unsafe by itself.

Security policy

The repository has no security policy, so users have no documented channel or process for reporting vulnerabilities. This reduces transparency but is secondary to the inactive project.

Version stability

Version 0.1 is not a stable major release, and no later versions provide evidence of maturation. The long period since publication reinforces the concern.