Tests, a changelog, and a clear MIT license improve transparency. Organization backing and a non-archived repository provide some continuity, but the missing security policy leaves maintenance practices less visible.
56%
Total Score
67
81
50
Only two releases exist, and none were published in the last 12 months; the latest release was nearly two years ago. This is substantial evidence of stalled maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the long release gap rather than showing ongoing maintenance.
Composer is used for the build, which fits the package ecosystem, but no security-scanning tooling is present. That leaves dependency and code-quality checks less visible.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though not evidence of unsafe code by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/sanctum Version ^3.2 | — | — |
illuminate/support Version ^9.0|^10.0|^11.0 | — | — |
illuminate/database Version ^9.0|^10.0|^11.0 | — | — |
illuminate/notifications Version ^9.0|^10.0|^11.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.