The MIT license, matching repository, and release notes improve transparency. Its small codebase has no tests, security policy, or security scanning, leaving limited evidence of ongoing maintenance.
48%
Total Score
50
70
50
The package has 16 releases and a healthy historical median interval of about 21 days, but it has had no releases in the last 12 months and the latest release was nearly four years ago. This strongly raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing little evidence of current maintenance.
Composer is used for the build, but no security scanning tools are configured. That is a maintenance and transparency gap for a package handling application authorization.
The repository has no security policy, leaving no documented path for reporting or handling vulnerabilities. This is a moderate transparency gap, though it does not by itself show the package is unsafe.
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.