The project is only 51 days old and all three recent commits come from one contributor. It has clear documentation, repository tests, a matching source repository, and a declared MIT license, but workflow references are unpinned and no security policy is present.
62%
Total Score
50
100
79
75
Only one registry account has publish access. That is consistent with the linked user-owned repository, but it leaves little publishing redundancy.
The registry and repository are owned by the same individual account, so there is no organization backing shown to compensate for the narrow maintainer base.
The package is only 51 days old with two releases, spaced about 14 days apart, so its maintenance record is still limited rather than established.
One contributor made all three commits in the last three months, creating a high dependency on a single maintainer.
There were three commits in the last three months, all during this young project's observed history; activity exists but does not yet demonstrate sustained maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/http Version ^11.0 || ^12.0 || ^13.0 | — | — |
zeevx/php-bachs Version ^0.1 | — | — |
illuminate/routing Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/support Version ^11.0 || ^12.0 || ^13.0 | — | — |
illuminate/contracts Version ^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.