License management plugin for Composer
69%
Total Score
caution
Usable with caveats: the registry release is nearly three years old and recent commit activity is absent.
The registry namespace and repository are owned by the same individual account, giving the package consistent ownership. It does not provide the broader continuity that organization backing might offer.
Only four releases exist, and none were published in the last 12 months; the latest registry release was nearly three years ago. This weakens evidence of ongoing release maintenance, although the repository has a later recorded push.
No commits or active maintainers were recorded in the last three months. The recent repository push is reassuring but does not demonstrate sustained recent development, so maintenance evidence remains mixed.
Composer build tooling is present, but no security scanning tool was detected. The missing scanner is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy. For a Composer plugin that runs during dependency operations, this leaves vulnerability-reporting and response expectations unclear.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.