The repository is maintained by one visible owner and has had no commits in three months, despite a recent release. Documentation, licensing, tests in the repository, and read-only workflow permissions are solid, but the two workflow actions are unpinned and no security policy is provided.
68%
Total Score
63
100
89
75
One registry account publishes the package. That is a limited publishing base for a user-owned project, though repository activity provides additional evidence of ownership.
The package and repository are tied to the same individual owner rather than an organization, so the project has limited visible institutional backing.
The package is over seven years old with 15 releases, but only one release in the last 12 months; this supports maturity while indicating a slow release cadence.
There were zero commits and zero active maintainers in the last three months. The recent release partly offsets this, but the current maintenance capacity is a meaningful concern.
Composer is used for builds, but no security scanning tools are reported. The missing scanner is a modest transparency gap rather than evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/events Version >=6.0 | — | — |
illuminate/support Version >=6.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.