sukohi/google-safe-browsing

Release historydanger

The latest release was published in March 2016, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment for a package integrating with an external security API.

Repo commit activitydanger

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

Repo popularitycaution

The repository has zero stars and zero forks, with one watcher. Popularity is only supporting evidence, but these figures provide little evidence of an active user or contributor community.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a maintenance and transparency gap, though it is less significant than the long inactivity period.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a transparency concern for a package whose purpose involves security-related checks.