# invl/retry — health index 38/100 (At risk)

> Inspection of the public repository invl/retry by inspect.software. It holds a health index of 38 out of 100, placing it in the At risk band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/invl/retry
- Report page: https://inspect.software/software/invl/retry
- Full JSON report: https://inspect.software/api/repositories/invl/retry/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/i/invl/retry.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.16.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 17/100 | Critical |
| Community & Adoption | 18% | 68/100 | Moderate |
| Sustainability & Governance | 24% | 38/100 | At risk |
| Engineering Quality | 20% | 50/100 | Moderate |
| Security | 16% | 21/100 | Critical |
| AI Readiness | not counted | 32/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | easy to use retry decorator in python |
| Primary language | Python |
| Stars | 757 |
| Forks | 110 |
| Created | 2014-05-21 |
| Last push | 2024-07-05 |
| Latest release | 0.9.2 |
| Commits (last year) | 0 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| pypi | retry | 0.9.2 | 35,379,950 |

## Vitality — 17/100 (Critical)

Is the project alive — is code being written and are releases shipping? Weight: 22% of the overall index.

### Development activity — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | not met | 0 / 36 | last push 745 days ago |
| Commit cadence | not met | 0 / 36 | 0/52 weeks with commits |
| Commit volume | not met | 0 / 18 | 0 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | partial | 16.2 / 27 | 14 version tags (no GitHub releases) |
| Release recency | not met | 0 / 36 | latest release 3722 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~81.8 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | maintenance record not established from the collected data |

## Community & Adoption — 68/100 (Moderate)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 18% of the overall index.

### Popularity & adoption — 68/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 46.7 / 60 | 757 stars |
| Forks | partial | 17 / 25 | 110 forks |
| Watchers | partial | 4.3 / 15 | 7 watchers |

### Community health — 44/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | partial | 16.9 / 22.5 | license file present, not a recognized license |
| CONTRIBUTING guide | not met | 0 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

### Ecosystem adoption (downloads) — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | met | 80 / 80 | 35,379,950 downloads/month across pypi |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 38/100 (At risk)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 24% of the overall index.

### Maintainer resilience (bus factor) — 15/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 0.7 / 22.5 | top contributor authored 97% of commits |
| Contributor breadth | partial | 4.1 / 13.5 | 3 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 27/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 14.3 / 46.8 | 31% of issues closed |
| PR acceptance | partial | 8.5 / 38.2 | 2/9 decided PRs merged |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

### Ownership & stewardship — 51/100 (Moderate)

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | partial | 10 / 30 | personal (user) account |
| Verified domain | excluded | 0 / 20 | not applicable to user accounts |
| Owner reach | partial | 9 / 25 | 17 followers of invl |
| Track record | partial | 21.8 / 25 | 21 public repos, account ~15 yr old |

### Package maintenance — 69/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 1 package(s) on pypi |
| Publish recency | partial | 4 / 35 | latest publish 3722 days ago |
| Version history | met | 20 / 20 | 14 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 50/100 (Moderate)

Are baseline engineering and documentation practices in place? Weight: 20% of the overall index.

### Engineering practices — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | tox.ini |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | met | 10 / 10 | — |

## Security — 21/100 (Critical)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 1/100 (Critical)

Excluded from scoring (no data or not applicable): Dependency lockfiles. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | not met | 0 / 30 | — |
| Dependabot config | not met | 0 / 25 | — |
| Dependency lockfiles | excluded | 0 / 25 | published library — lockfiles are an application concern, not expected |
| CodeQL workflow | not met | 0 / 20 | — |

### Dependency advisories — 100/100 (Excellent)

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:retry@0.9.2 runtime dependency closure — what installing the published package pulls in — 2 packages. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | met | 25 / 25 | no indirect dependency carries a known advisory |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 100/100 (Excellent)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 32/100 (At risk)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

### Agent context & guidance — 1/100 (Critical)

Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | not met | 0 / 45 | no CLAUDE.md / AGENTS.md / editor rules |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | excluded | 0 / 40 | no data |

### Verify loop (build / test / typecheck) — 46/100 (At risk)

Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | tox.ini |
| Static type checking | not met | 0 / 11 | — |
| Reproducible environment | not met | 0 / 10 | — |
| Demonstrated agent practice | excluded | 0 / 10 | no data |
| Automated maintenance | excluded | 0 / 8 | no data |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | Python without a type-check config |
| Manageable file sizes | met | 55 / 55 | 0/5 source files over 60KB |

## Collection warnings

- OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt