The license, README, release notes, and matching repository make the package straightforward to evaluate. Maintenance is the main concern: it has only two releases, no commits in the last three months, one registry maintainer, and no security policy.
62%
Total Score
50
88
75
Only one account has registry publish access. Because the project is user-owned rather than organization-backed, this leaves a thin publishing and continuity base.
The package has existed for over three years but has only two releases, with one release in the last 12 months and a median interval of about 2 years and 10 months. This indicates a slow maintenance cadence for a MediaWiki extension that may need compatibility updates.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release and push provide some counterweight, but the current maintenance signal is weak.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities in an authentication-related extension.
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.