Floppy-ameeRubyGems · Ruby

Verdict

Not enough signal to judge

We could not find enough public signal to judge Floppy-amee — 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 4414 days ago

Judged 4 days ago from signal heuristics. How each verdict is decided

latest 2.0.24
checked 4 days ago
registry ↗
repository ↗

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 3 checks

Commits 90d

—

Open issues

—

Unanswered

—

Contributors

—

State history 1

When	Change
2026-09-13	first verdict: unknown

Badge

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

[![maintenance](https://isitdeadyet.dev/badge/rubygems/Floppy-amee.svg)](https://isitdeadyet.dev/rubygems/Floppy-amee)

Watch it

Get told when Floppy-amee 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.