A concentrated contributor base and absent repository security scanning add modest maintenance risk. Licensing, release notes, and a clean workflow audit otherwise support adoption.
82%
Total Score
83
86
100
One contributor made 80% of the 15 recent commits, creating concentration risk. Three other contributors remained active, and the organization-owned project can provide some maintenance handoff capacity.
Composer build tooling is present, but no repository security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of unsafe code.
Version 0.13.0 is not a stable major release, and the README identifies the bundle as experimental, so backward-compatibility risk remains. It is not a prerelease and has no recent prerelease releases, which partly offsets that concern.
The only workflow uses a pull_request_target trigger, but the audit found no untrusted checkout or script-injection sink and no high- or medium-confidence findings. Its single action reference is unpinned, which is a minor reproducibility risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
mcp/sdk Version ^0.8.1 | — | — |
symfony/config Version ^7.3|^8.0 | — | — |
symfony/finder Version ^7.3|^8.0 | — | — |
symfony/console Version ^7.3|^8.0 | — | — |
symfony/routing Version ^7.3|^8.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.