The MIT license, focused dependency set, and matching repository make the package easy to audit. There is no repository security scanning, so operational assurance is limited.
60%
Total Score
0
100
75
75
The repository recorded zero commits and zero active maintainers during the last three months. For a package this young, that is a meaningful sign that maintenance may have stalled.
The package is only 211 days old with six releases, and releases were clustered into a very short median interval of about 16 minutes rather than showing a mature cadence. The latest release was about four months ago, leaving maintenance momentum uncertain.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest transparency and assurance gap rather than evidence of a defect.
The repository has no security policy. That leaves vulnerability-reporting expectations unclear, which modestly reduces operational transparency.
v0.6.0 is not a stable-major release, although it is not marked as a prerelease and recent releases were not prereleases. This indicates an early-stage API with possible compatibility changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework 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.