Dependency injection container library
82%
Total Score
67
100
94
75
All recent commits come from one contributor. Organization ownership provides some handoff capacity, but no second recent contributor is shown to share maintenance responsibility.
Two commits were made in the last three months by one active maintainer, which confirms recent activity but indicates a thin maintenance base.
Composer build tooling is present, but no security-scanning tool was detected, leaving a modest gap in repository hygiene.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a dependency library.
Both workflows were analyzed cleanly with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2 | — | — |
horde/exception Version ^3 || dev-FRAMEWORK_6_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.