intersight_clientRubyGems · Ruby

Verdict

Finished, not abandoned

intersight_client looks complete rather than neglected — no commits for over 4 years. all 1 open issues have had a reply. A library that has stopped changing is not the same as one that has been dropped.

health 39/100

Why this verdict?

finished — No commits for over 365 days, and almost nobody filing new issues — or the README says the project is done.

last commit 1537 days ago
almost no new issues — nobody is waiting on a fix

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

latest 0.1.5
licence Apache-2.0
stars 2
assessment attempted 10 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 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

What the project says about itself

Open milestones — Sprint 1/1 done; Sprint 2 (due 2021-12-17); Sprint 3 (due 2022-01-14) 1/1 done. Source: the repository's milestones.

Third-party facts checked 10 days ago; registry facts on every crawl.

State history 1

When	Change
2026-10-09	first verdict: finished

Badge

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

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

Watch it

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