Clear documentation, tests, and release notes make integration straightforward. The project remains active, though recent work is concentrated with one maintainer and CI uses a floating container image.
82%
Total Score
60
100
100
83
One registry publishing account is consistent with a user-owned project, but it leaves publishing access concentrated in one person.
The repository is owned by a user rather than an organization, so the single-maintainer and concentrated-contribution concerns are not offset by visible organizational backing.
One contributor made all 4 recent commits, so maintenance depends heavily on a single person; the established project and recent releases partly offset but do not remove that risk.
Only 3 issues and 3 pull requests are open, but there was no issue or pull request activity in the last month; this is a mild concern when combined with concentrated maintenance.
No repository security policy was found, leaving vulnerability reporting guidance less explicit for a package used in web applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nesbot/carbon Version ^2.0|^3.0 | — | — |
hashids/hashids Version ^4.0|^5.0 | — | — |
illuminate/database Version ^10.0|^11.0|^12.0|^13.0 | — | — |
whichbrowser/parser Version ^2.1 | — | — |
illuminate/container Version ^10.0|^11.0|^12.0|^13.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.