Usable with caveats, but risky for a new project because the last release was about 8 years ago and the repository has had no recent development. It has tests, release notes, a matching organization-backed repository, and no deprecation notice.
58%
Total Score
50
50
75
83
The repository recorded no commits and no active maintainers in the last 3 months. Combined with the old release date, this is the main abandonment risk for depending on the package.
The package declares 27 runtime dependencies, including a broad framework and payment-integration stack. This increases compatibility and maintenance burden, though the signal does not show dependency breakage or known instability.
The package has had no releases in the last 12 months, and its latest release was about 8 years ago. That long period without a release is a meaningful maintenance concern despite the earlier seven-release history.
There are 18 open issues and 2 open pull requests, with no issues or pull requests opened or closed in the last month. The unresolved backlog and lack of recent activity indicate weak ongoing maintenance.
The repository uses Composer build tooling, providing basic project build support, but it has no security-scanning tools. The missing scanning is a transparency and maintenance gap rather than evidence of maliciousness.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
carnage/cqrs Version ~0.2.0 | — | — |
carnage/cqorms Version ~0.3.0 | — | — |
doctrine/common Version ^2.6.0 | — | — |
carnage/zendfony-cli Version ~0.2.0 | — | — |
crossjoin/pre-mailer 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.