The GPL declaration conflicts with the repository's detected GPL-3.0 license, and the only workflow uses an unpinned action with a high-confidence template-injection finding. Strong tests, release notes, documentation, and organization backing provide useful transparency despite the lack of recent activity.
58%
Total Score
67
100
79
67
The manifest declares GPL-2.0-or-later, while the repository license file was detected as GPL-3.0. The release is licensed, but the mismatch creates avoidable legal ambiguity.
The package has 26 releases since June 2022, but none in the last 12 months; the latest release was in May 2025. This indicates a meaningful maintenance slowdown for a Drupal integration module.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the release gap, this is evidence of reduced maintenance capacity.
There are nine open issues and one open pull request, with no new or closed issues or merged pull requests in the last month. This suggests limited current project responsiveness.
Composer build tooling is present, but no security-scanning tools were detected. That is a modest transparency and assurance gap, not evidence of an unsafe release by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drupal/core Version ^9 || ^10 || ^11 | — | — |
composer/composer Version ^2 | — | — |
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.