The package has a clear README, license, and matching source repository. Its small dependency set and lack of install scripts reduce adoption friction, but missing security tooling and policy limit transparency.
38%
Total Score
0
100
64
75
The package has had no release in more than five years, with zero releases in the last 12 months and only four releases overall. This is strong evidence of abandonment risk for a still-prerelease package.
There were no commits or active maintainers in the last three months, consistent with the last push occurring in December 2020. This materially raises abandonment risk.
A license file is present and the package declares GPL-2.0+, but the detected artifact license is GPL-2.0. That mismatch creates some licensing uncertainty despite the otherwise clear licensing evidence.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance weakness for a package whose purpose is security-related.
The repository has no security policy. This leaves vulnerability reporting and response expectations undocumented, which reduces maintenance transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
drupal-composer/drupal-paranoia Version ~1 | — | — |
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.