The stable version and release notes make the project easier to follow. Its small user footprint and limited security process leave less evidence of resilience as a dependency.
68%
Total Score
50
86
50
One contributor made all two recent commits, giving the project a single-person maintenance dependency. The active release history partly compensates, but no second active contributor is shown.
The repository had two commits in the last three months, showing recent activity but at a low volume. This supports maintenance continuity without demonstrating a strong maintenance pace.
The repository has one star, zero forks, and one watcher, indicating a very small visible user and contributor base. Popularity is only supporting evidence, but this provides little external resilience.
Composer build tooling is present, but no security scanning tools were detected. For a Drupal project template, that leaves a meaningful gap in the visible release-quality process.
No repository security policy was found. This reduces transparency about how maintainers handle vulnerabilities, especially alongside the absence of security scanning.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ^13 | — | — |
composer/installers Version ^2.3 | — | — |
drupal/core-recommended Version ^11 | — | — |
niklan/composer-directories Version ^1.0 | — | — |
drupal/core-composer-scaffold Version ^11 | — | — |
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.