Usable with caveats: the package is licensed, documented, tested, and not deprecated, but it has had no release or repository commits for about two years and seven months. Its very small user footprint and absent security policy add maintenance and transparency concerns.
58%
Total Score
33
50
78
90
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and making abandonment risk a material concern.
Six runtime dependencies create meaningful transitive maintenance exposure for a small package, including several related project packages. The dependency count is not inherently unsafe but increases the number of components that must remain compatible.
The registry namespace and repository owner are different, but the repository is owned by an individual rather than an organization; this does not establish strong institutional backing or continuity.
Only one release exists, published about two years and seven months ago, with no releases in the last 12 months. This substantially weakens evidence of ongoing maintenance.
There is one open issue and no issues or pull requests were created or closed in the last month. This is weak evidence of active community or maintainer response.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
darling/roady-routes Version ^1.0 | — | — |
darling/php-darling-dev-tools Version ^1.0 | — | — |
darling/roady-module-utilities Version ^1.0 | — | — |
darling/php-unit-test-utilities Version ^1.0 | — | — |
darling/roady-routing-utilities Version ^1.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.