The project has had no commits or active maintainers in the last three months, and it lacks security scanning and a security policy. Its strong release history and organization-backed repository provide useful continuity, but the 200 runtime dependencies increase update and supply-chain exposure.
60%
Total Score
75
50
90
75
The package declares 200 runtime dependencies and no dev dependencies, creating a broad update and supply-chain surface. This may fit a Drupal project distribution, but it still increases dependency risk for consumers.
There were zero commits and zero active maintainers during the last three months, indicating that current maintenance activity has stalled.
Composer build tooling is present, but no security scanning tools were detected, leaving an avoidable gap in the project's security hygiene.
The repository has no security policy, so users are not given a documented route or process for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ovh/ovh Version v3.3.0 | — | — |
psy/psysh Version v0.12.4 | — | — |
behat/mink Version v1.11.0 | — | — |
drupal/core Version 10.5.2 | — | — |
drupal/imce Version 3.1.3 | — | — |
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.