Package Health/fond-of-spryker/google-custom-search

fond-of-spryker/google-custom-search

The README, MIT declaration, release notes, and modest dependency set make the package straightforward to adopt. The organization-backed repository is not archived, but it has had no commits or releases for about three and a half years, so future fixes are uncertain.

Latest 3.1.0

Packagist

60%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 10 releases and a regular historical interval, but its latest release was about three and a half years ago with none in the last 12 months. This materially raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly three-and-a-half-year release gap and weakening confidence in ongoing fixes.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project, though it is weaker evidence than the absent commits and releases.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Security policy

The repository has no published security policy, leaving no documented channel or process for handling security reports.