Tests and a clear MIT license improve adoption confidence, and the organization-backed repository makes ownership clear. The missing security policy and absent security scanning leave maintenance and response practices unclear.
38%
Total Score
50
79
50
The package has had only two releases, both in September 2017, with no releases in the last 12 months despite being nearly nine years old. This is strong evidence of abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since its last push in February 2018.
There is one open issue, but no new or closed issues and no pull-request activity in the last month, providing no evidence of ongoing support.
Composer build tooling is present, but no security-scanning tools are configured. That leaves an avoidable gap in ongoing dependency and code-health checks.
The repository has no security policy, so users have no documented process for reporting vulnerabilities or understanding the project's response expectations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
carnage/cqrs Version dev-master as 0.2.0 | — | — |
carnage/cqorms Version dev-master as 0.2.0 | — | — |
doctrine/common Version ^2.6.0 | — | — |
league/flysystem Version ^1.0 | — | — |
carnage/scheduler Version ~0.2.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.