# tsvsheet/go-tsvsheet — health index 51/100 (Moderate)

> Inspection of the public repository tsvsheet/go-tsvsheet by inspect.software. It holds a health index of 51 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/tsvsheet/go-tsvsheet
- Report page: https://inspect.software/software/tsvsheet/go-tsvsheet
- Full JSON report: https://inspect.software/api/repositories/tsvsheet/go-tsvsheet/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/t/tsvsheet/go-tsvsheet.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% | 72/100 | Good |
| Community & Adoption | 18% | 24/100 | Critical |
| Sustainability & Governance | 24% | 59/100 | Moderate |
| Engineering Quality | 20% | 69/100 | Moderate |
| Security | 16% | 21/100 | Critical |
| AI Readiness | not counted | 65/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | The tsvsheet engine as an importable Go library — parse, compute, and inspect .tsvt single-file spreadsheets |
| Primary language | Go |
| License | MIT |
| Stars | 0 |
| Forks | 0 |
| Created | 2026-07-16 |
| Last push | 2026-07-19 |
| Latest release | v0.7.0 |
| Commits (last year) | 22 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/tsvsheet/go-tsvsheet | v0.7.0 | — |

## Vitality — 72/100 (Good)

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

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 4 releases published |
| Release recency | met | 36 / 36 | latest release 0 days ago |
| Release cadence | met | 27 / 27 | a release every ~1 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 — 24/100 (Critical)

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 | 0 stars |
| Forks | not met | 0 / 25 | 0 forks |
| Watchers | not met | 0 / 15 | 0 watchers |

### Community health — 50/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| 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 | — |

## Sustainability & Governance — 59/100 (Moderate)

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 | not met | 0 / 22.5 | top contributor authored 100% of commits |
| Contributor breadth | partial | 1.4 / 13.5 | 1 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 100/100 (Excellent)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | met | 46.8 / 46.8 | 100% of issues closed |
| PR acceptance | excluded | 0 / 38.2 | no decided pull requests or no data |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | not met | 0 / 25 | 0 followers of tsvsheet |
| Track record | partial | 11.2 / 25 | 33 public repos, account ~0 yr old |

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

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

## Engineering Quality — 69/100 (Moderate)

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

### Engineering practices — 88/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 5 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .golangci.yaml |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 40/100 (At risk)

| 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 | not met | 0 / 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): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 8 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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 | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| 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 |

## AI Readiness — 65/100 (Moderate)

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) — 100/100 (Excellent)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .golangci.yaml |
| Static type checking | met | 11 / 11 | Go (statically typed) |
| Reproducible environment | met | 10 / 10 | lockfile |
| 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 — 99/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Go (statically typed) |
| Manageable file sizes | partial | 54.4 / 55 | 1/92 source files over 60KB |

## Collection warnings

- OpenSSF Scorecard did not return a usable result (Skipping github.com/tsvsheet/go-tsvsheet: run: internal error: ListCommits:error during graphqlHandler.setup: internal error: githubv4.Query: non-200 OK status code: 499  body: ""); 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