The package is young and maintained by one person, with no recorded commits in the last three months. It has a clear license, tests in the repository, recent releases, and a complete workflow audit, but its two actions are unpinned.
68%
Total Score
63
100
89
67
Only one registry account has publish access. This is a meaningful continuity risk for a young package because a single person represents the publishing base.
The registry and repository are owned by the same individual account, confirming direct ownership but providing no organizational backing to compensate for the single-maintainer risk.
No commits and no active maintainers were recorded in the last three months. Although the repository was pushed for this release, the observed short-term development activity is thin and raises maintenance risk.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, so this modestly limits external validation rather than determining health.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a hygiene gap, not evidence that the release is unsafe by itself.
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.