ueberbit/uebertool-companion

Registry deprecationdanger

Packagist marks the entire package as abandoned and names ueberbit/uebertool_companion as the replacement. This is a severe dependency risk even though the repository remains active.

Repo commit activitycaution

The repository recorded no commits and no active maintainers in the last three months. This conflicts with the recent registry releases and raises concern about current development activity.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That makes package ownership and publishing provenance less clear, even though a name mismatch can occur with subtree packaging.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were found. That is a meaningful transparency and maintenance gap for a dependency package.

Security policycaution

The repository has no security policy. This weakens the project's transparency for reporting and handling dependency issues.