mikelooper/ddd-cqrs

Release historydanger

The latest release was published about 2 years and 6 months ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package still presented as a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. This leaves bug fixes and compatibility work unsupported.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That raises a concrete concern that the published package may not be tied to the inspected repository.

Repo popularitycaution

The repository has 1 star, 0 forks, and 1 watcher. Low popularity is not decisive by itself, but it provides little external evidence of adoption or review.

Repo toolingcaution

The project uses Make and Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not evidence of unsafe code.