Healthy and actively maintained, with a clear source repository and frequent releases. The main caveats are the absence of packaged or repository tests, no changelog, and limited repository security-policy and workflow-permission hygiene.
82%
Total Score
75
100
83
80
Two registry maintainers are listed, while the repository shows two active contributors. This is a small but consistent publishing and development base.
A substantial README is present and the repository uses GitHub Releases, but neither the package nor repository contains tests or a changelog. The missing tests are a real maintenance and regression-risk gap for a feature-rich extension.
The repository is owned by a user account rather than an organization, so there is no organizational handoff capacity to offset the small contributor base.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides little external validation for a relatively new package.
Composer build tooling is present, but no security-scanning tools are configured. That is a transparency and maintenance gap, though active commits and clean workflow analysis provide some compensation.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^2.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.