It has a clear MIT license, tests, a changelog, and a matching organization-backed repository. CI actions are all unpinned, and the repository has no security policy, increasing maintenance and build-trust concerns.
48%
Total Score
50
71
50
The latest of only two releases was published over 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package remaining undeclared as deprecated.
There were no commits and no active maintainers in the last three months. Combined with the old last repository push, this materially raises the risk that defects will not be addressed.
Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, not a standalone reason to reject a small library.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers transparency, although it is less severe than the inactivity signals.
The assessed version is not a prerelease, but it remains on the 0.x major line, so compatibility maturity is limited. This matters less than the prolonged release inactivity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
clue/graph Version ~0.9.0|~0.8.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.