The project is new and all recent commits come from one contributor, leaving limited evidence of long-term maintenance capacity. Tests, a changelog, a matching repository, and a clear license improve confidence; workflow hardening is still incomplete.
70%
Total Score
67
86
75
The repository is owned by an individual user rather than an organization, so the single-contributor concentration is not offset by visible organizational backing.
The package is only 52 days old, with five releases concentrated over roughly four days; this shows active initial development but provides little long-term maintenance history.
One contributor made 100% of the recent commits, creating a meaningful continuity risk if that person becomes unavailable.
Composer build tooling is present, but no security-scanning tool was detected, leaving security hygiene less visible.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
moodle/moodle Version >=5.0 <5.3 | — | — |
moodle/composer-installer Version ^1.0 | — | — |
adamjenkins/moodle-local_oerexchange 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.