The package has a README, tests, a matching source repository, and an MIT declaration. Its Drupal/Drush scope is clear, but adopting an unmaintained 0.0.x release is a long-term liability.
35%
Total Score
25
67
50
The package has had only 3 releases, all concentrated in May 2017, with no releases in the last 12 months and no newer release after 2017. This is strong evidence of abandonment for a dependency intended to support evolving Drupal and Drush environments.
There were 0 commits and 0 active maintainers in the last 3 months, consistent with the last repository push being in 2017. This indicates no current maintenance capacity.
There has been no issue or pull-request activity in the last month, and one issue remains open. This reinforces the lack of recent project attention, although the small issue count is not itself severe.
Composer build tooling is present, which supports reproducible project structure, but no security-scanning tooling was detected. This is a modest hygiene gap rather than a standalone adoption blocker.
The repository has no security policy. For a small, old package this is a transparency gap, but it is secondary to the much stronger evidence of abandonment.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ^8.1 | — | — |
symfony/yaml Version ^2.8 | — | — |
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.