Clear licensing, documentation, and repository tests support adoption. Keep the dependency pinned because workflow action references are unpinned and the project lacks a security policy.
78%
Total Score
75
88
50
Three contributors were active, although the largest contributor made about 68% of recent commits; this is a moderate concentration risk rather than a severe single-maintainer failure.
The repository has only 3 stars and 2 forks, offering little external adoption evidence; low popularity is supporting context, not proof of poor maintenance.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and preventive-maintenance gap.
The repository has no security policy, so its process for receiving and handling vulnerability reports is not documented.
Both workflows were fully analyzed with no audit findings or untrusted-code sinks, but both of the two action references are unpinned, weakening build reproducibility and action supply-chain hygiene.
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.