carnage/cqrs

Release historydanger

Only four releases are recorded, with none in the last 12 months; the latest release was over 8 years ago, indicating a long-standing maintenance gap.

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, consistent with the repository's last push in 2017 and strong abandonment risk.

Package scaffoldingcaution

A README is present and gives useful architectural context, but it explicitly calls the project a work in progress and recommends maintaining a fork. The absent tests and changelog are normal for published package artifacts and are not treated as gaps.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected, leaving a modest transparency and maintenance-hygiene gap.

Security policycaution

The linked repository has no security policy, so there is no documented channel or process for handling vulnerability reports.