maatify/google-auth

Licensedanger

The manifest declares the package proprietary, with no detected license and no license file in either the artifact or repository. That leaves important legal and transparency uncertainty for an open-source dependency.

Package file treecaution

The artifact and repository each contain only composer.json and one PHP source file. That may fit a very small library, but it provides limited visible project substance and does not compensate for the licensing gap.

Release historycaution

The package has eight releases since May 2023, but none in the last 12 months; the latest release was about 13 months ago. This is meaningful evidence of slowing maintenance, though the release history is not empty.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Combined with no releases in the last 12 months, this points to currently inactive maintenance.

Repo package mentioncaution

The repository name does not match the package name, and no README package mention was available. A monorepo sub-package could explain the mismatch, but the repository's ownership of this package is not clearly established.