The declared MIT license, focused dependency set, and matching repository improve transparency. The individual maintainer and absent security policy leave limited evidence of ongoing support.
52%
Total Score
25
100
88
50
The repository had zero commits and zero active maintainers during the last three months. Combined with the short release history, this is meaningful evidence of slowed or paused maintenance.
One individual registry maintainer is responsible for publishing this package. That is a thin publishing base and provides limited resilience if maintenance stops.
The package has only three releases, all within its first 233 days, with a median interval of about 1.4 days. This shows a new project with limited evidence of sustained release practice.
Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance weakness rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities in an authentication-related extension.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^1.8.0 | — | — |
guzzlehttp/guzzle Version ^7.0 | — | — |
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.