# JetXu-LLM/llama-github — health index 61/100 (Moderate)

> Inspection of the public repository JetXu-LLM/llama-github by inspect.software. It holds a health index of 61 out of 100, placing it in the Moderate 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/JetXu-LLM/llama-github
- Report page: https://inspect.software/software/JetXu-LLM/llama-github
- Full JSON report: https://inspect.software/api/repositories/JetXu-LLM/llama-github/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/j/JetXu-LLM/llama-github.svg
- Inspected: 2026-07-21
- Methodology: metrics 1.13.0, report schema 0.17.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 70/100 | Good |
| Community & Adoption | 18% | 71/100 | Good |
| Sustainability & Governance | 24% | 45/100 | At risk |
| Engineering Quality | 20% | 72/100 | Good |
| Security | 16% | 48/100 | At risk |
| AI Readiness | not counted | 26/100 | Critical |

## Repository facts

| Field | Value |
|---|---|
| Description | Llama-github is an open-source Python library that empowers LLM Chatbots, AI Agents, and Auto-dev Solutions to conduct Agentic RAG from actively selected GitHub public projects. It Augments through LLMs and Generates context for any coding question, in order to streamline the development of sophisticated AI-driven applications. |
| Homepage | https://pypi.org/project/llama-github/ |
| Primary language | Python |
| License | Apache-2.0 |
| Stars | 291 |
| Forks | 23 |
| Created | 2024-05-16 |
| Last push | 2026-07-19 |
| Latest release | v0.4.5 |
| Commits (last year) | 12 |
| Bus factor | 1 |
| Topics | ai-agent, ai-code-generator, chatbot, code-generation, github, github-api, github-search, llm, python-library, retrieval-augmented-generation, jinaai, langchain |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| pypi | llama-github | 0.4.5 | — |

## Vitality — 70/100 (Good)

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

### Development activity — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 1 days ago |
| Commit cadence | partial | 4.2 / 36 | 6/52 weeks with commits |
| Commit volume | partial | 10 / 18 | 12 commits in the last year |
| OpenSSF Scorecard: Maintained | partial | 5 / 10 | 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |

### Release discipline — 92/100 (Excellent)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 30 releases published |
| Release recency | met | 36 / 36 | latest release 1 days ago |
| Release cadence | partial | 19.8 / 27 | a release every ~46.7 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### 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 — 71/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 39.9 / 60 | 291 stars |
| Forks | partial | 11.2 / 25 | 23 forks |
| Watchers | partial | 6.7 / 15 | 17 watchers |

### Community health — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (Apache-2.0) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

## Sustainability & Governance — 45/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) — 12/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 0.4 / 22.5 | top contributor authored 98% of commits |
| Contributor breadth | partial | 2.7 / 13.5 | 2 contributors |
| OpenSSF Scorecard: Contributors | not met | 0 / 10 | project has 0 contributing companies or organizations -- score normalized to 0 |

### Issue & PR responsiveness — 36/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 10.8 / 46.8 | 23% of issues closed |
| PR acceptance | partial | 25.5 / 38.2 | 4/6 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/30 approved changesets -- score normalized to 0 |

### 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 | 11.3 / 25 | 36 followers of JetXu-LLM |
| Track record | partial | 19.6 / 25 | 10 public repos, account ~11 yr old |

### Package maintenance — 100/100 (Excellent)

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

## Engineering Quality — 72/100 (Good)

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

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

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 3 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | no pull request found |

### Documentation — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://pypi.org/project/llama-github/ |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 12 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 48/100 (At risk)

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 — 48/100 (At risk)

Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| CI-Tests | excluded | 0 / 2.5 | no pull request found |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/30 approved changesets -- score normalized to 0 |
| Contributors | not met | 0 / 2.5 | project has 0 contributing companies or organizations -- score normalized to 0 |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | partial | 3.8 / 7.5 | 7 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5 |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | partial | 1.5 / 5 | dependency not pinned by hash detected -- score normalized to 3 |
| SAST | not met | 0 / 5 | no SAST tool detected |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | met | 7.5 / 7.5 | GitHub workflow tokens follow principle of least privilege |
| Vulnerabilities | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

## AI Readiness — 26/100 (Critical)

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) — 30/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 | not met | 0 / 11 | — |
| 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 | partial | 3 / 10 | dependency not pinned by hash detected -- score normalized to 3 |

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

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

### Machine-readable interfaces — 40/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | not met | 0 / 40 | — |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | met | 40 / 40 | examples |

## Collection warnings

- deps.dev does not index pypi:llama-github@0.4.5; advisories assessed against the repository dependency graph instead
- No resolved dependencies carried a version and a supported ecosystem

## 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