The package includes automated tests, a clear MIT license, and no install-time scripts. Its single-person ownership and repository naming mismatch reduce confidence that maintenance and package provenance will remain dependable.
52%
Total Score
50
100
79
67
The latest release was about three years ago, with no releases in the last 12 months. This is a meaningful maintenance concern for an extension, despite four releases overall.
There were no commits or active maintainers in the last three months. Combined with the old latest release, this points to a real risk of slowing maintenance.
There are five open issues and one open pull request, with no issues or pull requests opened or closed in the last month. This indicates limited recent project activity.
The repository name does not match the package name and its README does not mention the package. That makes the link between this Packagist release and the fetched repository less clear, even though the owner names are related.
The repository has no security policy. That weakens vulnerability-reporting transparency, although it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^1.0.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.