marvelley/google-books-api-client

Release historydanger

The package has only one release, published nearly 14 years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has not been maintained for years.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap and does not by itself establish a safety problem.

Repository archivedcaution

The repository is not archived, which is a modest positive, but its last push was about 10 years ago and does not offset the stale release and commit history.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a secondary transparency gap beside the much larger maintenance concern.