The MIT license, focused dependencies, tests, and release notes make this easy to evaluate and integrate. Organization backing and an unarchived repository provide some continuity, but no security policy leaves less formal support.
58%
Total Score
67
100
90
50
The latest release was about nine years ago, with no releases in the last 12 months. That strongly raises maintenance and compatibility risk for a library, although the seven-release history shows the project was previously established.
The repository had no commits and no active maintainers in the last three months, reinforcing that current maintenance is limited. The repository is not archived, but its recent inactivity remains a real adoption concern.
There were no new or closed issues or pull requests in the last month, with four open issues and two open pull requests. This is consistent with a low-activity project and provides little evidence of active support.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less serious than evidence of unsafe workflows or active compromise.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.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.