The MIT license, README, and release notes provide useful transparency for consumers. However, the project shows no recent maintenance, has a single individual maintainer, and provides no security policy or scanning evidence.
40%
Total Score
25
75
75
The latest release was nearly five years ago, and there have been no releases in the last 12 months. The package had 12 releases early in its life, but the prolonged release gap is strong abandonment evidence.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the nearly five-year release gap and indicating no visible ongoing maintenance.
Only one registry maintainer is listed, which creates a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
Composer build tooling is present, but no security scanning tools are configured. That reduces assurance around future dependency and code changes, although it is not evidence of malicious behavior.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a meaningful transparency gap for an access-control package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version 7.*|8.* | — | — |
santigarcor/laratrust Version 6.* | — | — |
sinarajabpour1998/log-manager Version 1.* | — | — |
sinarajabpour1998/alpha-helper Version 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.