The MIT license, focused file tree, and simple dependency set make the package easy to inspect. Its single maintainer, absent security policy, and roughly 18 months without a release or commit reduce confidence in ongoing support.
48%
Total Score
25
100
81
50
Only two releases were published, both within about two days, and there have been no releases in roughly 18 months. That short, inactive history provides weak evidence of ongoing maintenance.
There were no commits and no active maintainers in the last three months, consistent with the repository having gone quiet for roughly 18 months. This is a substantial abandonment concern.
The repository is owned by an individual account rather than an organization, so there is no shown organizational continuity to compensate for the inactive maintenance record.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. For a package that processes application database schemas, this leaves vulnerability reporting and response expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^9|^10|^11 | — | — |
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.