The repository has four open issues and three open pull requests with no recent resolution, while security scanning and a security policy are absent. MIT licensing, a matching repository, and a usable README provide useful transparency, but do not offset the long maintenance gap.
42%
Total Score
25
79
50
The latest release was in May 2020, with no releases in the last 12 months. That long gap is strong evidence of abandonment risk for a maintained integration package.
The repository had 0 commits and 0 active maintainers in the last 3 months, consistent with the prolonged release gap and indicating no visible ongoing maintenance.
Four issues and three pull requests remain open, with no new or closed issues or pull requests in the last month. This suggests outstanding maintenance needs are not being actively handled.
Composer build tooling is present, but no security-scanning tools were detected. This weakens supply-chain maintenance hygiene, although it is not evidence that the package is malicious.
The repository has no security policy. That limits transparency about vulnerability reporting and response, especially for a package integrated into Laravel applications.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.