A clear README, tests, and changelog make adoption easier. Maintenance rests with one contributor, and the repository has no security policy or scanning; pin a reviewed release and monitor updates.
70%
Total Score
75
100
93
50
One contributor made 100% of the 14 commits in the last three months. That creates a meaningful continuity risk if the maintainer becomes unavailable.
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence of a malicious package.
The repository has no security policy, leaving no documented process for reporting and handling vulnerabilities.
The audit analyzed all three workflows with no high-confidence findings or untrusted checkout and script-injection paths. However, all five action references are unpinned, and one workflow grants top-level write permissions, creating avoidable supply-chain and token-scope hygiene risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
moodle/moodle Version ^5.0 | — | — |
moodle/composer-installer 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.