The MIT license, matching repository, and clear README provide good transparency for consumers. The lack of security scanning and a very small project footprint add maintenance risk.
46%
Total Score
50
88
50
The latest release was published nearly five years ago, with no releases in the last 12 months. Earlier releases were regular, but the long current gap is a substantial abandonment concern.
There were no commits or active maintainers in the last three months, reinforcing the release-history concern and indicating that maintenance has effectively stopped.
There were no new or closed issues or pull requests in the last month, with open work still present. This adds evidence of low current project activity.
Composer build tooling is present, but no security-scanning tools were detected. For a developer-facing coding tool this is a modest transparency and maintenance gap, not a release blocker.
The repository has no security policy. This makes vulnerability reporting less clear, though it is a hygiene concern rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
drupal/coder Version ^8.3.13 | — | — |
drupol/php-conventions Version ^5 | — | — |
drupol/phpcsfixer-configs-drupal 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.