Documentation, licensing, and release packaging are in good shape. The project is backed by an organization, but recent work comes from one contributor and its workflow actions are not pinned. Repository naming and README references also do not clearly identify this package.
68%
Total Score
67
100
88
83
All two recent commits came from one contributor. Organizational backing provides some handoff capacity, but no second active contributor is shown.
Only two commits were recorded in the last three months, which is limited activity, although the recent release history indicates the project is not abandoned.
The repository name does not match the package name and its README does not mention the package, so the source-package relationship is less transparent than expected.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency gap.
The repository has no security policy, making vulnerability reporting and response expectations less explicit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
poliander/cron Version ~3.0 | — | — |
composer/installers Version ~1.0|~2 | — | — |
mwstake/mediawiki-componentloader Version ~1 | — | — |
mwstake/mediawiki-component-processmanager Version ~6 | — | — |
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.