jordikroon/google-vision

The MIT license, substantial README, comprehensive tests, and GitHub release notes provide useful transparency for consumers. The modest dependency set and lack of install-time scripts reduce packaging risk, but compatibility should be tested against current PHP and Google Vision behavior.

Latest 1.8.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 25 releases since June 2017, but no registry releases in the last 12 months and its latest release was in November 2019. This is strong evidence of long-term maintenance inactivity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release history showing no recent maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 5 issues and 2 pull requests remain open. This suggests unresolved project activity rather than active stewardship.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy. This is a transparency and maintenance gap, though it is less severe than the absence of releases or commits.