# braintrustdata/braintrust-sdk-go — health index 68/100 (Moderate)

> Inspection of the public repository braintrustdata/braintrust-sdk-go by inspect.software. It holds a health index of 68 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/braintrustdata/braintrust-sdk-go
- Report page: https://inspect.software/software/braintrustdata/braintrust-sdk-go
- Full JSON report: https://inspect.software/api/repositories/braintrustdata/braintrust-sdk-go/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/b/braintrustdata/braintrust-sdk-go.svg
- Inspected: 2026-07-22
- Methodology: metrics 1.13.0, report schema 0.26.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 93/100 | Excellent |
| Community & Adoption | 18% | 40/100 | At risk |
| Sustainability & Governance | 24% | 62/100 | Moderate |
| Engineering Quality | 20% | 85/100 | Excellent |
| Security | 16% | 50/100 | Moderate |
| AI Readiness | not counted | 83/100 | Good |

## Repository facts

| Field | Value |
|---|---|
| Description | Braintrust Go SDK |
| Homepage | https://www.braintrust.dev/ |
| Primary language | Go |
| License | Apache-2.0 |
| Stars | 7 |
| Forks | 2 |
| Created | 2025-10-31 |
| Last push | 2026-07-17 |
| Latest release | v0.10.0 |
| Commits (last year) | 191 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/braintrustdata/braintrust-sdk-go | v0.10.0 | — |

## Vitality — 93/100 (Excellent)

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

### Development activity — 89/100 (Excellent)

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

### Release discipline — 100/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 | 21 releases published |
| Release recency | met | 36 / 36 | latest release 4 days ago |
| Release cadence | met | 27 / 27 | a release every ~10.2 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 | last human commit 4 days ago |

## Community & Adoption — 40/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 12.6 / 60 | 7 stars |
| Forks | not met | 0 / 25 | 2 forks |
| Watchers | not met | 0 / 15 | 0 watchers |

### Community health — 70/100 (Good)

| 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 | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

## Sustainability & Governance — 62/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) — 37/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 4.7 / 22.5 | top contributor authored 79% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 12 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 8 contributing companies or organizations |

### Issue & PR responsiveness — 58/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 13.7 / 46.8 | 29% of issues closed |
| PR acceptance | partial | 33.7 / 38.2 | 88/100 decided PRs merged |
| OpenSSF Scorecard: Code-Review | partial | 10.5 / 15 | Found 10/14 approved changesets -- score normalized to 7 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 17.2 / 25 | 244 followers of braintrustdata |
| Track record | partial | 19.6 / 25 | 97 public repos, account ~3 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 4 days ago |
| Version history | met | 20 / 20 | 24 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 85/100 (Excellent)

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

### Engineering practices — 82/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 4 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | .golangci.yml |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | partial | 18 / 20 | 20 out of 21 merged PRs checked by a CI test -- score normalized to 9 |

### Documentation — 90/100 (Excellent)

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

## Security — 50/100 (Moderate)

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

Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | partial | 6.8 / 7.5 | binaries present in source code |
| Branch-Protection | excluded | 0 / 7.5 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| CI-Tests | partial | 2.2 / 2.5 | 20 out of 21 merged PRs checked by a CI test -- score normalized to 9 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | partial | 5.2 / 7.5 | Found 10/14 approved changesets -- score normalized to 7 |
| Contributors | met | 2.5 / 2.5 | project has 8 contributing companies or organizations |
| Dangerous-Workflow | not met | 0 / 10 | 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 | met | 7.5 / 7.5 | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | met | 5 / 5 | all dependencies are pinned |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | not met | 0 / 7.5 | 26 existing vulnerabilities detected |

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | AGENTS.md, CLAUDE.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | met | 40 / 40 | 76 of 89 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 92/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | met | 18 / 18 | Makefile, examples/internal/autoinstrumentation/Makefile, examples/internal/mise.toml, examples/internal/temporal/mise.toml, mise.toml |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .golangci.yml |
| Static type checking | met | 11 / 11 | Go (statically typed) |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | met | 10 / 10 | 23 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | met | 10 / 10 | all dependencies are pinned |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Go (statically typed) |
| Manageable file sizes | met | 55 / 55 | 0/174 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 |

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