gflocatorRubyGems · Ruby

Verdict

Not enough signal to judge

We could not find enough public signal to judge gflocator — no repository resolved from its registry metadata.

health 38/100

Why this verdict?

unknown — No repository resolved from the registry metadata, and no recent release either.

no repository resolved from registry metadata; last release 5085 days ago

Judged today from signal heuristics. How each verdict is decided

latest 0.0.1
checked today
registry ↗

Vulnerabilities, end of life and next steps

Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.

Review remediation options →

Maintenance trends

Loading historical repository activity…

Signals · last 1 check

The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.

Commits 90d

—

Open issues

—

Unanswered

—

Contributors

—

State history 1

When	Change
2026-09-27	first verdict: unknown

Badge

Drop this in your README. It re-renders itself as the verdict changes.

[![maintenance](https://isitdeadyet.dev/badge/rubygems/gflocator.svg)](https://isitdeadyet.dev/rubygems/gflocator)

Watch it

Get told when gflocator changes state, changes licence, or is deprecated — instead of finding out during an incident.

Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.