The repository has had no commits or active maintainers in the last three months, and it has no security policy. Its recent release history and clear migration notes provide useful transparency, but the project is still young and has little community traction.
68%
Total Score
50
100
88
88
The package and repository are owned by the same individual account, with no organization backing shown. That is consistent ownership but indicates a relatively thin apparent support base.
The repository recorded zero commits and zero active maintainers during the last three months. Because the package is young and had a recent release, this is a meaningful maintenance concern but not proof of abandonment.
The repository has zero stars, forks, and watchers, providing no community adoption or review signal. Popularity is supporting evidence, so this lowers confidence in project maturity without deciding the result alone.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a hygiene concern for a package that manages application database structures.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ^13.0 | — | — |
illuminate/contracts Version ^13.0 | — | — |
spatie/laravel-package-tools Version ^1.16 | — | — |
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.