A clear README, changelog, stable versioning, and organization backing make the package understandable to adopt. Its eight runtime dependencies and lack of security scanning add maintenance uncertainty for a server component.
45%
Total Score
50
79
75
The latest release was published in June 2018, with no releases in the last 12 months; the package has had no release for about eight years. This is strong evidence of abandonment risk despite its earlier release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates that maintenance has effectively stopped.
There were no new or closed issues or pull requests in the last month, and no open issues or pull requests. This is consistent with an inactive project, although it does not independently prove abandonment.
Composer and Phing provide build tooling, but no security-scanning tools were detected. The build setup is a modest positive, while the lack of scanning is a maintenance and assurance gap.
The linked repository has no security policy. For a DNS server, the absence of a documented vulnerability-reporting path reduces transparency and makes future security maintenance harder to assess.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version * | — | — |
rhumsaa/uuid Version ~2.8 | — | — |
monolog/monolog Version 1.10.* | — | — |
appserver-io/logger Version ~2.0 | — | — |
appserver-io/server Version ~10.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.