The single maintainer and lack of security scanning reduce resilience if issues emerge. The package is well documented, tested, licensed, and its repository remains active rather than archived, but its maintenance pace is currently quiet.
67%
Total Score
50
100
86
75
Only one registry account can publish releases, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is limited evidence of broader continuity.
The repository is owned by an individual rather than an organization, providing no visible institutional backing. This reinforces the single-maintainer continuity concern.
The package has existed since June 2013 and has 18 releases, but none in the last 12 months; the latest release was over a year ago. This indicates a meaningful slowdown for a maintained dependency.
There were zero commits and zero active maintainers in the last three months, consistent with the absence of releases in the last year. This is the clearest maintenance concern.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/yaml Version ^5.4|^6|^7 | — | — |
symfony/framework-bundle Version ^5.4|^6|^7 | — | — |
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.