Usable with caveats: the package is licensed, documented, tested, and not deprecated or archived, but it has had no release in nearly seven years and no recent repository activity. Treat it as a stable legacy dependency and verify compatibility with your Laravel version before adopting it.
52%
Total Score
50
100
75
75
The package has 29 releases and a rapid historical release interval, but its latest release was nearly seven years ago with no releases in the last 12 months. That long period without a new release is a meaningful maintenance concern.
There were no commits and no active maintainers in the last three months, with the repository last pushed nearly seven years ago. This is the strongest practical sign that ongoing compatibility and maintenance should not be expected.
Composer build tooling is present, but no security scanning tools are configured. For a small, old package this is a transparency gap, though it is less significant than the demonstrated lack of recent maintenance.
The linked repository is not archived, so it remains open to maintenance even though its last push was nearly seven years ago. The non-archived status is positive, but the age of the last push is consistent with the broader maintenance concern.
The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations, especially for a package used in API applications.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.