Licensing, tests, and a changelog provide useful project substance. Organizational backing helps, but unresolved issues and missing security guidance increase adoption risk.
42%
Total Score
50
50
75
50
The latest registry release was about eight years ago, with no releases in the last 12 months. The historical median interval was about 82 days, so the current release gap is a substantial maintenance concern.
The repository had zero commits and zero active maintainers in the last three months. Combined with the old registry release, this is strong evidence of inactive maintenance.
The package declares 13 runtime dependencies, including the application platform and Composer itself. This is a sizeable dependency surface that adds maintenance burden, but the signal does not show an unusually unsafe dependency pattern.
The package runs post-install and post-update Composer scripts. These increase installation complexity and execution exposure, although they are not by themselves evidence of abandonment.
There are 38 open issues and three open pull requests, with no new or closed issues and no merged pull requests in the last month. This indicates weak current issue handling.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
oro/platform Version 1.8.* | — | — |
beberlei/assert Version 2.* | — | — |
monolog/monolog Version 1.8.0 | — | — |
hwi/oauth-bundle Version 0.3.9 as 1.0 | — | — |
composer/composer Version 1.0.0-p2 as 1.0.0-p1 | — | — |
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.