It has a stable MIT release, clear README, matching source repository, and release notes for this version. The single maintainer, absent security policy, and limited recent activity reduce confidence in ongoing support.
62%
Total Score
50
100
88
83
Only one account has registry publish access. Because the repository is user-owned rather than organization-backed, this leaves a thin publishing and support base.
The package has 22 releases over more than 10 years, but none in the last 12 months and its latest registry release was about 18 months ago. This indicates slowed maintenance, despite its long release history.
There were no commits and no active maintainers in the last three months. This is a meaningful maintenance concern, although the repository's recent push status provides some compensating evidence.
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe.
The linked repository has no security policy. For a package handling invitation flows and email-based access, this weakens the project's vulnerability-reporting transparency.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/events Version ^5.8|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/support Version ^5.8|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0|^12.0 | — | — |
illuminate/database Version ^5.8|^6.0|^7.0|^8.0|^9.0|^10.0|^11.0|^12.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.