Documentation, tests, licensing, and release notes are all in good shape. The organization-backed project is current, but recent work is concentrated in one contributor and its workflow dependencies are not pinned; there is also no security policy or scanning tool.
72%
Total Score
67
100
94
67
One contributor made 100% of the 1 recent commit. Organization backing helps provide continuity, but no second active contributor is shown in this period.
Only 1 commit was recorded in the last 3 months, so recent source activity is thin even though the package has a current release.
Composer build tooling is present, but no security scanning tool was detected, leaving a repository assurance gap for an authorization library.
The repository has no security policy, which makes vulnerability reporting and response expectations less transparent for a security-sensitive authorization component.
The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, or audit findings, but all 5 action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
casbin/casbin Version ~4.0 | — | — |
illuminate/console Version ~10.0|~11.0|~12.0|~13.0 | — | — |
illuminate/support Version ~10.0|~11.0|~12.0|~13.0 | — | — |
illuminate/database Version ~10.0|~11.0|~12.0|~13.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.