giantbomb/giantbomb-php-api

Release historydanger

The latest release was in December 2013, with no releases in the last 12 months and only nine releases overall. This long period without published updates is strong evidence of abandonment risk.

Repo commit activitydanger

There were no commits and no active maintainers during the last three months. Combined with the old last release, this indicates that practical maintenance has stopped.

Dependency profilecaution

The package has three runtime dependencies, including PHP, Guzzle, and Doctrine Cache. This is a manageable dependency surface, though old dependencies may create compatibility concerns in an unmaintained package.

Repo toolingcaution

Composer is used as a build tool, but no security scanning tools are present. The missing scanning is a modest hygiene gap rather than the main risk for this package.

Security policycaution

The repository has no security policy. This reduces transparency around vulnerability reporting, although the package's much older maintenance history is the larger concern.