Clear documentation, tests, release notes, and licensing make integration straightforward. The project lacks a security policy, has no security scanning, and all three workflow actions are unpinned.
62%
Total Score
50
100
78
75
One registry maintainer is consistent with the linked repository being owned by an individual, but it leaves limited publishing redundancy.
The registry namespace and repository belong to the same individual account, providing consistent ownership context but no organizational backing or redundancy.
There are only two releases, both clustered within about three days, so the package has limited observed maturity despite being about 328 days old.
The repository recorded zero commits and zero active maintainers in the last three months, with the last push about 10 months ago; this is the clearest abandonment concern.
The repository has zero stars and one fork. This is weak supporting evidence, but popularity alone does not determine health for a small package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/auth Version ^10.0 || ^11.0 | — | — |
illuminate/support Version ^10.0 || ^11.0 | — | — |
illuminate/database Version ^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.