The MIT license, README, changelog, and matching repository make adoption transparent. Unpinned workflow actions and no security policy leave maintenance hygiene weaker.
58%
Total Score
75
100
83
50
The latest of four releases was published over two years ago, with no releases in the last 12 months. This is strong evidence of stalled maintenance for a package that may need compatibility updates.
The repository recorded zero commits and zero active maintainers in the last three months. That supports the conclusion that development is currently inactive.
The linked repository has no security policy. That reduces transparency about how vulnerabilities are reported and handled, especially for a package that manages Heroku configuration.
The sole workflow was fully analyzed and has no detected dangerous triggers or audit findings, but both of its two action references are unpinned. That leaves its build automation exposed to changing upstream action code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
illuminate/support Version * | — | — |
php-heroku-client/php-heroku-client Version * | — | — |
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.