carnage/cqorms
The small codebase has limited project hygiene and no security policy. Its MIT license and matching repository are positives, but the package remains a substantial abandonment risk for new dependencies.
31%
Total Score
33
69
67
Health Score Breakdown
The latest release was in December 2017, with no releases in the last 12 months. This long period without published maintenance is a strong abandonment concern.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's prolonged release inactivity.
The package contains a small, focused 12-file implementation and its repository tree matches the artifact, which supports transparency but provides little evidence of mature project infrastructure.
A README is present, and the absence of tests or a changelog in the published artifact is normal packaging practice. The README is very short, so it offers limited consumer guidance.
The repository is owned by a user account rather than an organization, so there is no shown organizational backing to compensate for the thin maintenance evidence.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 carnage/cqrs Version ^0.2.0 | — | — |
jms/serializer Version ^1.1.0 | — | — |
doctrine/doctrine-orm-module Version ^1.0.0 | — | — |
zendframework/zend-servicemanager Version ^2.5 || ^3.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.