Usable with caveats: the repository is organization-backed, not archived, and the package is small with a simple dependency profile. However, the latest release is a beta from over five years ago and there has been no recorded commit activity in the last three months, so ongoing maintenance is uncertain.
58%
Total Score
75
100
79
50
The latest release was published over five years ago, with no releases in the last 12 months. This is a meaningful maintenance concern despite the package having six releases and a previously regular release interval.
There were no commits and no active maintainers recorded in the last three months. Combined with the old latest registry release, this raises abandonment risk.
The repository uses Composer, which provides expected build tooling, but it has no reported security scanning. For this small package the missing scanner is a hygiene gap rather than a severe risk.
No security policy was found in the source repository, reducing transparency about how vulnerabilities would be reported and handled.
The only workflow lacks a top-level token-permissions declaration. No write permissions or other dangerous workflow behavior were observed, so this is a limited workflow-hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ~9||~10 | — | — |
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.