The README is marked WIP and its Composer installation example names a different package. There is no security policy or automated security scanning, which leaves this small project with limited transparency.
43%
Total Score
0
100
69
83
The repository recorded zero commits and zero active maintainers in the last three months, despite being only about five months old. This indicates limited ongoing maintenance.
No license is declared, no license file is present in the package, and the repository also has no license file. That creates a real legal and adoption risk.
The package is 155 days old but has only one release, with no demonstrated release cadence. That is weak evidence of maturity for a dependency.
The repository name matches the package, reducing the risk of an unrelated repository, but the README does not mention the package name. This weakens package-to-source traceability.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version >=5.4.0 | — | — |
jennoramcaj/resource-query Version ^0.2.3|dev-master | — | — |
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.