vipsoft/code-coverage-extension

Release historydanger

The package has had no releases in over 12 years, despite five releases overall. This is strong evidence of abandonment risk, though the stable version and intact repository provide limited compensation.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this indicates no current maintenance capacity.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while three issues and two pull requests remain open. This suggests unresolved maintenance needs and little visible response.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are detected. This is a modest transparency and maintenance gap rather than a severe risk on its own.

Security policycaution

The repository has no security policy. For an old package with no current activity, this leaves users without a clear reporting or response process.