The stable release, clear README, and matching source repository make adoption easier. A single maintainer, no security policy, and unpinned workflow actions leave less maintenance and build assurance.
61%
Total Score
50
100
81
83
The package and repository are owned by the same individual, so the source linkage is coherent, but there is no organization backing shown to provide additional continuity.
The package has had three releases, all clustered around December 5–6, 2024, and none in the following 21 months. That makes ongoing maintenance uncertain despite the package being small and focused.
There were no commits and no active maintainers in the last three months. For a small extension this may reflect stability, but it still reduces evidence of current maintenance.
The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but this provides little external evidence of adoption or community support.
Composer is used for builds, but no security-scanning tools are configured. This is a modest transparency and assurance gap rather than a standalone severe risk.
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.