Automatically push new Flarum discussion posts to a Facebook Page
78%
Total Score
healthy
Active project with clear licensing and recent releases, but workflow permissions and unpinned actions need attention.
Only one registry account can publish releases, which creates publishing concentration. Repository activity from two contributors partly offsets the maintenance concern, but not the registry access concentration.
The repository is owned by the same individual namespace as the package and is user-owned rather than organization-owned. This matches the single registry maintainer and provides no organizational handoff evidence.
The repository has zero stars, forks, and watchers. This is limited supporting evidence for adoption and review, but the package is young and active, so it does not outweigh the maintenance signals.
Composer is used as a build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and hygiene gap rather than a standalone severe risk.
The repository has no security policy, leaving no documented process for reporting vulnerabilities or coordinating fixes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
flarum/core Version ^2.0 | — | — |
guzzlehttp/guzzle Version ^7.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.