The MIT license and complete source tree make the code easier to inspect and reuse. No security policy or security scanning adds uncertainty for a package with no active maintainer activity.
38%
Total Score
0
64
50
The package has had no release in over five years and none in the last 12 months; its 11-release history shows an early burst followed by a long stop. This is strong abandonment evidence.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history's prolonged inactivity.
The repository has zero stars and forks and only one watcher, providing little evidence of community adoption or independent visibility. Popularity is supporting evidence, but it reinforces the maintenance concern.
Composer build tooling is present, but no security scanning tools were found. That leaves automated detection of dependency and build risks uncovered.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^0.1.0-beta.16 | — | — |
flarum/tags Version ^0.1.0-beta.16 | — | — |
v17development/flarum-blog Version * | — | — |
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.