Package Health/revolution/authorize-google-api

revolution/authorize-google-api

The package is small and clearly documented, with a matching source repository, a stable release, and no install-time scripts. Its six-year release and commit silence makes future compatibility and maintenance uncertain, with no security policy or automated security scanning to add confidence.

Latest 1.1.0

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in March 2020, with no releases in the last 12 months and only three releases overall. This long period without updates is a substantial abandonment and compatibility concern.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history's prolonged inactivity. The repository is not archived, but there is no recent activity compensating for the stale release.

Maintainers

Only one registry publishing account is listed, and the repository owner is an individual. Combined with the observed inactivity, this suggests limited maintenance capacity, though registry access records alone are not proof of abandonment.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. Given the package's long inactivity, the missing automated security checks reduce confidence in ongoing maintenance hygiene.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations and handling procedures unclear. This is a hygiene and transparency concern, not evidence of malicious behavior.