The repository is compact and has basic tests, a clear license, and a stable release record. Organization backing helps offset the limited recent contributor base, but the absent security policy leaves transparency weaker.
72%
Total Score
67
88
75
All recent commits came from one contributor, so maintenance currently depends on a single active person. The organization-owned project provides some handoff capacity, but no second active contributor is shown.
Only one commit was recorded in the last 3 months, showing limited recent activity despite the package's strong release cadence. This modestly increases maintenance risk.
The repository name does not match the package name and its README does not mention the package. Although naming differences can occur for extensions, this leaves some uncertainty that the linked repository directly represents the published package.
The repository uses Composer build tooling, but no security-scanning tool was detected. This is a transparency and hygiene gap, not evidence that the package is unsafe.
No repository security policy was found. For an authentication extension, this weakens the documented process for reporting and handling security issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/installers 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.