Recent releases and three active contributors support continued maintenance. The organization-backed project has tests and licensing, but workflow hygiene and the repository's lack of a package reference reduce transparency.
68%
Total Score
100
100
88
83
The repository name does not match the package name and its README does not mention the package. Although name differences can occur in subpackages, the absence of any README reference makes package ownership less transparent.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a component that handles authentication and API communication.
The only workflow was fully analyzed without untrusted checkouts or script-injection findings, but all five action references are unpinned. Two high-confidence template-injection findings are hygiene concerns here because no relevant untrusted trigger or sink was reported.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mwstake/mediawiki-componentloader Version ~1 | — | — |
mwstake/mediawiki-component-token-authenticator Version ~1 | — | — |
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.