It has a clear MIT license, useful documentation, release notes, and only one runtime dependency. Maintenance appears inactive since February 2025, while the small user base, absent security policy, and unpinned workflow actions add ongoing risk.
55%
Total Score
50
100
86
67
All three releases were made around February 2025, followed by about 20 months with no release in the collected history. This indicates a maintenance gap for a relatively new package.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped after the initial release period.
The repository has zero stars and one fork, showing limited visible adoption. Popularity is supporting evidence rather than a verdict, but it provides little evidence of a broad maintenance community.
The repository has no security policy, leaving no documented channel or process for reporting and handling vulnerabilities.
Both workflows were analyzed successfully with no reported audit findings or dangerous triggers, but both use action references without pinning. This is a supply-chain hygiene weakness, not a severe risk on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^1.8.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.