The package is clearly identified, permissively licensed, and has a small, understandable dependency footprint. Its unresolved TODOs, absent security policy, and lack of security scanning add transparency and maintenance concerns.
42%
Total Score
0
100
67
83
The package has had no release in more than five years, and there were zero releases in the last 12 months. This is strong evidence of abandonment risk despite its 11 historical releases.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
The project uses Composer for builds, but no security-scanning tools were detected. The absence is a modest supply-chain hygiene concern, though it does not by itself show unsafe code.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for an extension that manages user sessions.
Version 0.2.7 is not a stable-major release, so the package offers less maturity assurance than a 1.x release. It is not marked prerelease, which partially offsets that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version >=0.1.0-beta.15 <0.1.0-beta.16 | — | — |
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.