A single maintainer and no security scanning leave limited resilience, while the workflow uses three unpinned actions. The MIT license, focused package tree, README, and repository tests provide useful transparency.
61%
Total Score
33
50
88
83
There were no commits and no active maintainers in the last three months, and the repository was last pushed about four years ago; this is the strongest abandonment concern.
Nine runtime dependencies, including framework components, a date library, and Guzzle, create a moderate dependency surface that can increase maintenance coupling.
Only one registry maintainer is listed, leaving little visible publishing redundancy, although the repository is owned by the same individual.
The registry namespace and repository are owned by the same individual account, which supports ownership consistency but provides no organizational backing.
The package has three releases, but none in the last 12 months and its latest registry release was about 19 months ago, indicating a slow maintenance cadence.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
morilog/jalali Version ^3.2 | — | — |
illuminate/http Version ^7.0|^8.0|^9.0 | — | — |
guzzlehttp/guzzle Version ^6.5.5|^7.0.1 | — | — |
illuminate/support Version ^7.0|^8.0|^9.0 | — | — |
illuminate/contracts Version ^7.0|^8.0|^9.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.