moro/platform-cms

Release historydanger

The latest release was published in December 2017, with no releases in the last 12 months despite a history of 21 releases. This long period without a release is a substantial abandonment concern.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the last release being in 2017, this indicates a sustained lack of maintenance.

Dependency profilecaution

The package declares 31 runtime dependencies, spanning its framework, database, UI assets, mail, and monitoring. That broad dependency surface increases maintenance and compatibility risk for an already inactive project.

Project backingcaution

The repository is owned by an individual user rather than an organization. This does not prove poor stewardship, but it provides no organizational backing to compensate for the inactive maintenance record.

Repo toolingcaution

The repository uses Composer for builds, but no security-scanning tools were detected. For a CMS with a broad runtime dependency set, that is a meaningful security-maintenance gap.