There is no security policy or automated security scanning, and its only workflow grants top-level write access. The MIT license, release notes, README, and matching repository improve transparency.
66%
Total Score
50
86
50
The package is newly published, with 17 releases in less than one day and a zero-day median interval. That rapid initial sequence provides little evidence of an established maintenance pattern.
No commits or active maintainers were recorded in the last three months, which is a maintenance concern; however, the repository was pushed recently and the package is brand-new.
Composer is used for builds, but no security-scanning tools are present. This is a modest transparency and assurance gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow was fully analyzed and has no untrusted checkout, injection, or audit findings, but it grants top-level write permissions across the workflow, which is broader than necessary.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^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.