There are no automated tests, security policy, or security scanning, and the lone maintainer limits continuity. The package does include a usable README, has no install-time scripts, and its repository is not archived.
38%
Total Score
25
75
75
The latest release was published over eight years ago, with no releases in the last 12 months. That is strong evidence of abandonment for a Laravel integration package.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.
Neither the package nor the linked repository declares or contains a recognized license file. This creates a material adoption and redistribution risk.
The registry lists one maintainer. The repository is organization-owned, which provides some backing context, but the absence of recent commits means there is no observed maintenance activity to compensate for the thin publishing base.
The repository has no security policy, and no security scanning tools were reported by the repository tooling signal. This weakens transparency for a package handling profiles, storage, and network services.
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.