The package is clearly documented and tested, with a license and active recent work. Its single-contributor base, very short release history, and unpinned workflow actions leave more maintenance and build-integrity risk than a mature dependency.
64%
Total Score
75
71
50
Only two releases exist and both were published today, roughly six hours apart. This shows recent activity but provides little evidence of long-term maintenance or release stability.
One contributor made all 11 commits in the last three months, concentrating maintenance knowledge in a single person and increasing abandonment or handoff risk.
The repository name matches the package, reducing the risk of an unrelated source link, but its README does not mention the package name. That weakens confidence that the repository documentation explicitly identifies the published package.
Composer is used as a build tool, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of unsafe code.
The repository has no security policy, leaving vulnerability reporting and disclosure expectations unspecified.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
moodle/moodle Version ^5.2 | — | — |
moodle/composer-installer Version ^1.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.