mindgruve/wordpress

Release historydanger

The package has had no releases in about nine years, with zero releases in the last 12 months; this is strong evidence that the release is no longer maintained.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating effectively inactive development.

Repo popularitycaution

The repository has zero stars and zero forks, with four watchers. Popularity is only supporting evidence, but these low engagement levels provide little evidence of active community oversight.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. This is a meaningful hygiene gap, though it does not by itself show unsafe code.

Security policycaution

The linked repository has no published security policy, leaving no documented process for reporting and handling vulnerabilities in a package that ships a large application.