Healthy and suitable to depend on, with minor transparency and security-process caveats. It has a stable release history, active repository with two recent contributors, tests, a README, and organization backing; the main concerns are zero repository popularity, no security policy or scanning, and the repository not explicitly naming the package in its README.
82%
Total Score
100
100
83
80
The repository name does not exactly match the package name and its README does not mention the full package name, creating some uncertainty about the repository-to-package linkage. However, the repository path and file contents clearly describe the File Storage Utilities component, so this remains a caution rather than a severe concern.
The repository has zero stars, forks, and watchers, providing no community-adoption evidence. This is a supporting weakness, not a health verdict, because the package has other evidence of active maintenance and organization backing.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanning process is a modest transparency gap rather than evidence that the release is unsafe.
The repository has no SECURITY.md or other security policy, leaving vulnerability-reporting expectations unclear.
The sole GitHub Actions workflow has no top-level token permissions declaration. Although no write permissions were detected, explicitly restricting permissions would provide stronger CI security hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mwstake/mediawiki-componentloader 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.