The repository remains maintained enough to be usable, with tests, release notes, and active build and dependency tooling. However, the package has had no registry release in over four years, no recent commits, and all 16 workflow actions are unpinned.
68%
Total Score
50
100
94
67
The repository is owned by an individual rather than an organization, so the single registry maintainer is consistent with the project’s backing model. This provides limited redundancy if that maintainer stops contributing.
The latest release was published in May 2022, with no releases in the last 12 months. This is a meaningful freshness concern for a dependency, although the package has a long release history and the repository was pushed more recently.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this raises abandonment risk.
There are five open pull requests and one open issue, but none were opened or closed in the last month. This indicates some unresolved project activity rather than a fully active maintenance stream.
The repository has no security policy. This is a transparency gap, though it is partly offset by the presence of Dependabot scanning.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ~1.0 | — | — |
symfony/yaml Version ~4.0 | — | — |
symfony/config Version ~4.0 | — | — |
symfony/console Version ~4.0 | — | — |
symfony/http-kernel Version ~4.0 | — | — |
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.