The single maintainer and absent security controls leave limited resilience. MIT licensing, stable versioning, low runtime dependency count, and recent releases provide useful counterweight.
65%
Total Score
67
100
90
50
Only one registry publishing account is listed, which creates continuity risk. The organization-owned repository provides some backing, but it does not demonstrate a broader active maintainer base.
The repository recorded no commits and no active maintainers in the last three months, despite a recent registry release. This weakens confidence in ongoing source maintenance.
Composer is used for build tooling, but no security scanning tools are present. This is a transparency and maintenance gap, though not a severe risk on its own.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers maintenance transparency for a package intended for application integration.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drupal/generate_style_theme Version dev-3x|^3.0.1|4.x-dev|^4.0|^5.0|5.x-dev | — | — |
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.