domraider/libdns

The MIT license, focused dependency set, and matching organization repository provide clear ownership and basic transparency. Its tiny audience and absent security policy add modest concern, but the long period without activity is the main adoption risk.

Latest 1.1.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly nine years: its latest release was in April 2017, with zero releases in the last 12 months. This is strong evidence of abandonment risk despite the package not being deprecated.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing that development stopped years ago.

Repo popularity

The repository has one star, zero forks, and one watcher, indicating very limited community validation. Popularity is supporting evidence only, but it offers little compensation for the long inactivity period.

Repo tooling

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

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations unclear. This matters more because the project also shows no recent maintenance activity.