Documentation, tests, and release notes make the starter project easy to evaluate. Organization backing and a long release history help, but the repository lacks a security policy and scanning coverage.
68%
Total Score
67
100
94
50
The repository recorded zero commits and zero active maintainers over the last three months. This is a meaningful recent maintenance gap, partly offset by the release published on May 29, 2026.
There are only three open issues and three open pull requests, with no new or closed items in the last month. This suggests limited recent collaboration, though the small queue is not by itself severe.
Composer build tooling is present, but no security scanning tools were detected. For a Drupal starter project with many dependencies, that weakens supply-chain maintenance hygiene.
The repository has no security policy. That makes vulnerability reporting and response expectations less transparent, although it does not establish abandonment on its own.
The only workflow grants top-level write permissions and has both uses unpinned; the audit also reports high-confidence trusted-publishing use. No untrusted checkout or script-injection path was found, limiting this to workflow hygiene caution.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ^13.3 | — | — |
composer/installers Version ^2.3 | — | — |
webflo/drupal-finder Version ^1.2 | — | — |
drupal/core-recommended Version ~11.3.5 | — | — |
fourkitchens/sous-admin Version dev-main | — | — |
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.