The organization-owned repository matches the package and includes consumer documentation and a changelog. Its workflow uses broad write permissions and unpinned actions, while no security policy is present.
57%
Total Score
75
100
90
50
The package has only one release in its 98-day history, so there is too little release history to establish mature maintenance. No deprecation signal offsets this, but the package is still relatively new.
The repository had zero commits and zero active maintainers in the last three months, leaving current maintenance capacity unproven. Its recent push aligns with the sole release, which reduces but does not remove the concern.
The linked repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled. The organization-owned project provides some backing, but no documented process is shown.
The only workflow gives top-level write permissions, uses both analyzed actions without pinning, and has a high-confidence template-injection finding. No untrusted checkout or injection trigger was detected, so these are workflow-hygiene concerns rather than a severe standalone risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
moodle/moodle Version 3.5.* || 3.6.* || 3.7.* || 3.8.* || 3.9.* || 3.10.* || 3.11.* || 4.0.* || 4.1.* || 4.2.* || 4.3.* || 4.4.* || 4.5.* || 5.0.* || 5.1.* || 5.2.* | — | — |
composer/installers Version ~1.0 || ~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.