Clear documentation, licensing, and regular project activity support continued maintenance. Workflow hygiene and the missing security policy leave additional trust gaps for a package that runs build and release automation.
67%
Total Score
100
79
50
The registry marks the package deprecated at package scope, with a replacement listed as the same package name. This is a meaningful adoption warning, although the active repository and recent releases show the project itself has not been abandoned.
The project uses Make and Composer for builds, but no security scanning tools were detected. The missing scanning layer is a modest transparency and maintenance concern.
No repository security policy was found. For a maintained theme with build and release automation, this leaves vulnerability-reporting expectations unclear.
Both workflows use unpinned actions, and the release workflow has six high-confidence template-injection findings. Because no pull_request_target, workflow_run, untrusted checkout, or script-injection sink was reported, these remain workflow hygiene concerns rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drupal/core Version ^10 | — | — |
drupal/stable Version ^2.0 | — | — |
drupal/smart_trim Version ^2 | — | — |
drupal/ui_patterns Version ^1.5 | — | — |
drupal/twig_field_value Version ^2.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.