Usable with caveats: it is licensed, tested, documented, and not deprecated, but maintenance appears to have stopped after only two releases in 2019. Treat it as a legacy development dependency and verify compatibility before adopting it.
52%
Total Score
25
100
75
75
The package has only two releases, with the latest published on February 3, 2019 and none in the last 12 months. This is a substantial maintenance and abandonment concern.
There were zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for years and creating meaningful abandonment risk.
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the thin maintainer base and long inactivity.
Composer build tooling is present, but no security scanning tools were detected. For this small, old project that is a modest transparency gap rather than evidence that the package is unsafe.
The repository is not formally archived, but it was last pushed on February 3, 2019. That old repository state reinforces the maintenance concern shown by the release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.0 | — | — |
prooph/event-store Version ^7.5 | — | — |
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.