cmsgears/template-blog

Release historydanger

The latest release was nearly five years ago, with no releases in the last 12 months and only seven releases overall. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. This materially weakens confidence in ongoing maintenance.

Dependency profilecaution

The template declares 62 runtime dependencies across many modules, plugins, widgets, and frontend assets. That breadth increases upgrade and compatibility risk for an inactive project.

Repo toolingcaution

Composer is used for builds, which fits the package, but no security-scanning tools are configured. The missing automated security coverage is a transparency and maintenance gap.

Security policycaution

The linked repository has no security policy. This leaves vulnerability reporting and maintenance expectations undocumented, adding a modest transparency concern.