It has a clear MIT license, a focused dependency set, and a documented release change. Pin 0.1.1 while the project establishes a longer maintenance record.
70%
Total Score
75
100
75
75
One person has registry publishing access. Because the repository is user-owned rather than organization-backed, the package has a thin apparent maintainer base and limited succession evidence.
The package is newly published, with two releases on the same day and no longer-term release history. This limits evidence of sustained maintenance, though the short age makes the absence of a longer cadence expected.
Composer is used as the build tool, but no security-scanning tool was detected. The missing scanning is a modest transparency gap for a new package.
The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a hygiene gap, not a standalone severe risk.
Version 0.1.1 is not a stable major release, so its API and behavior may still change. It is not marked prerelease, which provides some compensating maturity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^2.0 | — | — |
guzzlehttp/guzzle Version ^7.7 | — | — |
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.