Clear licensing, a useful README, and organization-backed ownership improve confidence. The repository has gone three months without commits, and all nine workflow actions are unpinned; missing security scanning and a policy add smaller maintenance gaps.
61%
Total Score
67
93
75
The repository recorded zero commits and zero active maintainers in the last three months. Recent release and push evidence partly compensates, but the lack of current development lowers maintenance confidence.
There were no new or closed issues and no merged pull requests in the last month, with 10 open issues remaining. This supports the concern about limited current maintenance, though it is not evidence of abandonment by itself.
Composer build tooling is present, but no security scanning tools were detected. That is a maintenance and transparency gap rather than a severe dependency risk.
The repository has no published security policy, leaving vulnerability reporting and response expectations unclear for a project template used in deployments.
The single workflow was fully analyzed with no reported audit findings or dangerous triggers, but all nine action references are unpinned. The absence of a top-level permissions block is acceptable on its own.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drush/drush Version ^12.0 | — | — |
composer/installers Version ^1.12 | — | — |
drupal/core-recommended Version ^10.0@stable | — | — |
cweagans/composer-patches Version ^1.7 | — | — |
drupal/localgov_microsites Version ^4.0 | — | — |
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.