denwebdev/google-oath2

Consumer documentation is missing, and the project has no security policy or security scanning. Stable licensing and a small dependency set reduce—but do not remove—the maintenance concern.

Latest v3.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The published artifact has no README, which makes integration harder for consumers of this library. Missing tests and changelog files are expected packaging gaps here and do not independently lower health.

Release history

The package has had no release in nearly seven years, and it published no releases in the last 12 months. Its 14-release history shows prior development but does not offset the long current pause.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the last push occurring in 2019. This is strong evidence of an abandoned or unmaintained dependency.

Repo popularity

The repository has zero stars, forks, and watchers, providing no community adoption or review signal. Popularity is only supporting evidence, but this reinforces the thin-maintenance picture.

Repo tooling

Composer is used for the build, which is appropriate, but no security scanning tooling is present. That leaves a modest transparency and maintenance gap alongside the stale activity.