This is a healthy, actively developed release with a stable version line, regular releases over the 188-day package lifetime, a non-archived organization-owned repository, strong README and test coverage, clear package structure, and a matching source repository. The main concerns are that all 23 recent commits came from one contributor, the repository has no security policy or security-scanning tooling, and there is no changelog; these are meaningful transparency and resilience gaps but do not outweigh the observed release and maintenance activity.
82%
Total Score
75
100
94
90
One contributor made all 23 commits in the last 3 months, creating a genuine continuity and bus-factor concern; organization ownership provides some capacity for handoff but does not demonstrate a second active maintainer.
There are no open issues or pull requests and no recent issue or pull-request activity. This is not a strong negative for a young package with ongoing commits, but it provides little evidence of a broader support community.
Composer build tooling is present, but no security-scanning tools are configured. The missing scanning coverage is a hygiene gap rather than evidence of abandonment.
The repository has no SECURITY.md or other detected security policy, leaving vulnerability-reporting expectations unclear for dependents.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/routing Version ^10.0|^11.0|^12.0|^13.0 | — | — |
illuminate/support Version ^10.0|^11.0|^12.0|^13.0 | — | — |
spatie/browsershot Version ^4.0|^5.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.