blueroger/cms-extensions

Release historycaution

Only two releases exist, with the latest published about six months ago and a median interval of about five days; this is a young, lightly established release history rather than evidence of mature maintenance.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the link between the published package and source repository is less transparent than expected.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counters provide no independent evidence of broader review or adoption.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.

Security policycaution

The repository has no security policy, so there is no documented channel or process for reporting vulnerabilities.