30hills/cms_seed

Release historydanger

The latest release was published over seven years ago, with no releases in the last 12 months; the three-release history does not show ongoing maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the prolonged release gap rather than showing a merely slow cadence.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, providing no evidence of current project response or maintenance activity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving an additional maintenance and vulnerability-detection gap.

Security policycaution

The linked repository has no security policy, leaving no documented channel or process for handling vulnerability reports; the long maintenance gap makes this more consequential.