A single release appeared in the last four years, and repository activity has been absent since October 2022. The package is licensed, documented, and not archived or deprecated, but its beta status and unpinned workflow actions add uncertainty for a new dependency.
45%
Total Score
50
100
71
67
The package has only 3 releases, all concentrated around October 2022, with 0 releases in the last 12 months and a package age of about 4 years. This is strong evidence of abandonment risk for a dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with no meaningful activity since October 2022. This materially increases abandonment risk.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap, not a standalone reason to reject the package.
The repository has no security policy. That weakens vulnerability-reporting transparency, especially for a package that has seen no recent maintenance.
The assessed release is still a prerelease beta, and all recent releases are prereleases. That limits maturity and signals that consumers may face unresolved compatibility or stability issues.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^1.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.