Documentation is substantial, and this release includes version-specific notes. The focused dependency set and matching repository help, but the project shows limited recent activity and lacks a security policy or scanning.
58%
Total Score
50
75
50
One registry maintainer creates a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintainer capacity to compensate.
The package is about 19 months old with six releases, but only one release in the last 12 months. That indicates noticeably slower maintenance for a still-young package.
The repository had zero commits and zero active maintainers in the last three months. For a young package, that is a meaningful abandonment concern even though a release was published within the last year.
Composer build tooling is present, but no security-scanning tools were detected. This is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. That reduces transparency about how vulnerabilities are reported and handled, especially for a package intended for API development.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/database Version ^v11.43.2 | — | — |
spatie/laravel-data Version ^4.13.1 | — | — |
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.