The package has a clear README, a matching source repository, stable versioning, and no install-time scripts. Organization backing helps, but security documentation and automated scanning are absent.
68%
Total Score
67
88
75
The package has had no registry release in the last 12 months, with the latest release more than two years ago. Recent repository commits partly offset this, but the release cadence remains a maintenance concern.
All recent commits came from one contributor. Organization ownership provides some handoff capacity, but no second active contributor is shown to reduce concentration risk.
Two commits were recorded in the last three months, showing some recent activity, but the pace is modest for a package with no recent registry release.
Composer is used for the build, but no security-scanning tool was detected. This is a transparency and maintenance-hygiene gap rather than a severe risk on its own.
The repository has no security policy, leaving reporting and response expectations undocumented for users and maintainers.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ^10.5 || ^11 || ^12 | — | — |
laravel/prompts Version * | — | — |
drupal-code-builder/drupal-code-builder Version ^4.2.0 | — | — |
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.