The beta release and two unpinned workflow actions add avoidable uncertainty for production adoption. Clear licensing, release notes, a matching repository, and no install scripts provide useful safeguards, but the small release history and recent lack of commits suggest limited maintenance capacity.
62%
Total Score
50
81
75
The package has only two releases over about four years, with a median gap of roughly three years and eight months; one release in the last 12 months shows it is not abandoned, but cadence is sparse.
The repository recorded zero commits and zero active maintainers in the last three months, which is a meaningful maintenance concern despite a push recorded in the repository_archived signal.
Composer build tooling is present, but no security-scanning tooling was detected; this is a modest transparency and maintenance gap for a small package.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities.
The assessed release is v2.0.0-beta.1, so it is not yet stable for production use even though it represents the current major version.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^2.0.0-beta | — | — |
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.