Clear tests, a changelog, licensing, and recent work support adoption. The repository has no security policy, and its 11 workflow actions are all unpinned, while the repository does not clearly identify the package.
78%
Total Score
100
88
83
The repository name does not match the package name and its README does not mention the package, creating uncertainty that the linked source repository is specifically for this release.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users are given no documented channel or process for reporting security issues.
Both workflows were fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all 11 action references are unpinned, which weakens build reproducibility and increases dependency drift risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
elgg/elgg Version ~7.0.0 | — | — |
composer/installers 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.