Healthy and reasonable to adopt, with some project-hygiene caveats. It is actively maintained, licensed, correctly linked to its repository, and has a stable release, but it is young, has no tests or changelog, and lacks a security policy.
78%
Total Score
75
100
83
80
Only one registry account has publishing access. That is consistent with the single-user project ownership, but it leaves registry publishing dependent on one account.
A substantial README is present, but neither the artifact nor repository contains tests or a changelog. For a feature-rich extension, the missing tests are a meaningful maintenance gap, while the missing changelog is a lesser transparency concern.
The package and repository are owned by the same individual account. This provides clear ownership, though it lacks the handoff capacity of organization backing.
The repository has no stars, forks, or watchers. This does not establish a health problem for a young package, but it provides no external adoption evidence.
Composer build tooling is present, but no security-scanning tools are configured. The build setup is adequate, while the missing scanning is a modest security-process gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^2.0 | — | — |
flarum/messages 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.