The documented API, tests, matching repository, and MIT license are useful foundations. However, development stopped in July 2019 and the package remains at an initial 0.1 release, so its Symfony-era integration may require maintenance work.
42%
Total Score
50
71
83
The last release was in June 2019, with no releases in the past 12 months and only four releases overall. This is strong evidence of abandonment risk for a framework integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
The linked repository is not archived, but its last push was in July 2019. The non-archived status avoids a severe abandonment classification, while the old push still aligns with the activity concerns.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a hygiene gap, but it is secondary to the much older maintenance evidence.
Version v0.1.2 is not a stable major release, so API compatibility and long-term support are less certain. The lack of recent releases reinforces that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^2.8 || ^3.0 || ^4.0 | — | — |
symfony/config Version ^2.8 || ^3.0 || ^4.0 | — | — |
symfony/console Version ^2.8 || ^3.0 || ^4.0 | — | — |
chaplean/api-client-bundle Version ^1.0 | — | — |
symfony/dependency-injection Version ^2.8 || ^3.0 || ^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.