timelsass/wp-php-version-check

Release historydanger

The latest release was published in May 2017, and there have been no releases in more than 9 years. That strongly raises abandonment risk for a dependency, even though the package is not marked deprecated.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with a project that has been inactive for years. This materially increases the risk that defects or compatibility changes will go unaddressed.

Maintainerscaution

One registry maintainer is reasonable for a small user-owned package, but it provides limited visible maintenance capacity when combined with the long absence of releases and commits.

Repo toolingcaution

The repository uses Composer, which fits the package, but no security scanning tooling was detected. This is a hygiene gap rather than evidence that the package is unsafe.

Security policycaution

No security policy was found. For a small, inactive package this reduces transparency about vulnerability reporting and response, although it is less significant than the maintenance evidence.