The package is documented and has repository tests, a changelog, and a matching source repository. Its only 2016 release and absent security policy leave maintenance and security practices too uncertain for a new forum deployment.
38%
Total Score
58
50
This is the package's only release, published about 10 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk despite the repository still being available.
The artifact declares and includes an MIT license, but the README describes the application as GPL-3.0. This license mismatch creates avoidable adoption and compliance uncertainty.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of a specific vulnerability.
The repository is not archived, which provides some continuing availability, but its last push was also about 10 years ago and does not offset the stale release history.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a security-sensitive forum application.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
composer/composer Version 1.0.0-alpha11 | — | — |
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.