The package has clear licensing, tests, documentation, and a stable release. Its small single-person project has shown no commits or issue activity for three months, and no security policy is present.
64%
Total Score
50
100
81
83
One registry maintainer is consistent with a personal project, but it leaves the package dependent on a single publisher without organizational backing.
The registry and repository are owned by the same individual account, confirming coherent ownership but offering no organizational continuity if that maintainer stops work.
Three releases were published during the first day, but there have been no later releases across the package's 130-day lifetime, leaving its longer-term maintenance unproven.
There were zero commits and zero active maintainers during the last three months. For a package only 130 days old, that is a meaningful sign that maintenance may have stopped after the initial release burst.
There were no new or closed issues or pull requests in the last month. With zero open issues, this is ambiguous rather than strong evidence of abandonment, but it provides no sign of an active user or maintainer community.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version ^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.