The package has a matching repository, a useful README, and only one runtime dependency. Long-term transparency is weaker because there is no license, security policy, test suite, or security scanning, while recent activity is limited.
56%
Total Score
50
100
71
75
No license is declared, detected, or present in the package or repository. This creates a real adoption and transparency concern for a reusable Laravel library.
The package is mature, with 35 releases since 2018, but only one release in the last 12 months. That suggests a currently slow release cadence, partly offset by the recent release of this version.
There were zero commits and zero active maintainers in the preceding three months. The recent release provides some compensation, but the observed development activity remains thin.
Composer build tooling is present, but no security scanning tools were detected. For an access-control package, the lack of repository security scanning is a modest transparency gap.
The repository has no security policy. That makes vulnerability reporting and maintainer response expectations less clear for a package handling authorization logic.
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.