# jyswee/buggazi — health index 31/100 (At risk)

> Inspection of the public repository jyswee/buggazi by inspect.software. It holds a health index of 31 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/jyswee/buggazi
- Report page: https://inspect.software/software/jyswee/buggazi
- Full JSON report: https://inspect.software/api/repositories/jyswee/buggazi/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/j/jyswee/buggazi.svg
- Inspected: 2026-07-20
- Methodology: metrics 1.13.0, report schema 0.16.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 29/100 | Critical |
| Community & Adoption | 18% | 32/100 | At risk |
| Sustainability & Governance | 24% | 36/100 | At risk |
| Engineering Quality | 20% | 31/100 | At risk |
| Security | 16% | 27/100 | Critical |
| AI Readiness | not counted | 37/100 | At risk |

## Repository facts

| Field | Value |
|---|---|
| Description | Project management for coding agents: bugs, features, sprints, as easy as git. CLI + MCP server (71 tools, local or remote). |
| Homepage | https://buggazi.ai |
| Primary language | Shell |
| Stars | 1 |
| Forks | 0 |
| Created | 2026-07-03 |
| Last push | 2026-07-14 |
| Commits (last year) | 12 |
| Bus factor | 1 |
| Topics | ai-agents, bug-tracker, claude-code, cli, cursor, developer-tools, jira-alternative, mcp, mcp-server, project-management |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | buggazi | 2.12.0 | 8,843 |

## Vitality — 29/100 (Critical)

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

### Development activity — 48/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 5 days ago |
| Commit cadence | partial | 2.1 / 36 | 3/52 weeks with commits |
| Commit volume | partial | 10 / 18 | 12 commits in the last year |
| OpenSSF Scorecard: Maintained | not met | 0 / 10 | project was created within the last 90 days. Please review its contents carefully |

### Release discipline — 1/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | not met | 0 / 27 | no releases published |
| Release recency | not met | 0 / 36 | no releases |
| Release cadence | not met | 0 / 27 | no releases |
| 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 — 32/100 (At risk)

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

### Popularity & adoption — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | not met | 0 / 60 | 1 stars |
| Forks | not met | 0 / 25 | 0 forks |
| Watchers | not met | 0 / 15 | 0 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) — 66/100 (Moderate)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 52.6 / 80 | 8,843 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

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

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

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

Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 46.8 | no issues or no data |
| PR acceptance | excluded | 0 / 38.2 | no decided pull requests or no data |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/12 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 46/100 (At risk)

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 | 2.2 / 25 | 1 followers of jyswee |
| Track record | partial | 24.5 / 25 | 51 public repos, account ~11 yr old |

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

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

## Engineering Quality — 31/100 (At risk)

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

### Engineering practices — 1/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | not met | 0 / 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 — 75/100 (Good)

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

## Security — 27/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 — 27/100 (Critical)

Excluded from scoring (no data or not applicable): CI-Tests, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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/12 approved changesets -- score normalized to 0 |
| Contributors | partial | 0.8 / 2.5 | project has 1 contributing companies or organizations -- score normalized to 3 |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | partial | 2.2 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | project was created within the last 90 days. Please review its contents carefully |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | excluded | 0 / 5 | no dependencies found |
| 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 | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

## AI Readiness — 37/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 — 75/100 (Good)

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

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

### Verify loop (build / test / typecheck) — 1/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | not met | 0 / 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 | excluded | 0 / 10 | no dependencies found |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | Shell without a type-check config |
| Manageable file sizes | met | 55 / 55 | 0/1 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

- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- deps.dev does not index npm:buggazi@2.12.0; advisories assessed against the repository dependency graph instead

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