The clear README, matching repository, and stable 1.0.1 release make the project understandable to adopt. A single maintainer and absent security policy leave limited resilience if problems emerge.
48%
Total Score
25
70
50
Only two releases exist, with the latest published in June 2021 and none in the last 12 months. For a Drupal project template, this long release gap is a substantial abandonment concern.
The repository had zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release inactivity. No provided signal shows compensating recent maintenance.
The registry lists one maintainer, leaving a thin publishing base. This is a resilience concern for a user-owned project, though it does not by itself show that the package is unfit.
Composer build tooling is present, but no security scanning tools were detected. That weakens automated oversight somewhat, although the package's long inactivity is the more important concern.
The linked repository has no security policy, leaving no stated channel or process for reporting vulnerabilities. This is a modest transparency and maintenance concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drupal/mysql56 Version ^1.0 | — | — |
drupal/core-recommended Version ^9 | — | — |
cweagans/composer-patches Version ^1.7 | — | — |
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.