The MIT license, clear README, and matching source repository make the package easier to evaluate. Composer packaging is present, but the project lacks a security policy and automated security scanning. Its broad Laravel integration surface also increases the cost of taking on an apparently dormant dependency.
44%
Total Score
0
71
50
This is the only release, published about four years ago, with no releases in the last 12 months. That strongly limits evidence of ongoing maintenance.
The repository recorded no commits and no active maintainers in the last three months, consistent with the package's long period without releases. This is a substantial maintenance and abandonment concern.
Composer build tooling is present, but no security scanning tools were found. That weakens ongoing supply-chain hygiene, although it is not by itself evidence that the package is unsafe.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a backend package.
The latest version is v0.0.1 and is not a stable major release, which suggests an immature release line. The release does include documented notes, but that does not offset the lack of subsequent versions.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ibrand/setting Version ~1.0 | — | — |
maatwebsite/excel Version ~2.1.23 | — | — |
ibrand/laravel-sms Version ~1.0 | — | — |
encore/laravel-admin Version 1.5.19 | — | — |
laravel-admin-ext/backup Version 1.0.2 | — | — |
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.