# shanjunmei/dig — health index 49/100 (At risk)

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

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 75/100 | Good |
| Community & Adoption | 18% | 39/100 | At risk |
| Sustainability & Governance | 24% | 47/100 | At risk |
| Engineering Quality | 20% | 36/100 | At risk |
| Security | 16% | 41/100 | At risk |
| AI Readiness | not counted | 53/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | dig is a compile‑time code generation based DI tool for Go. It provides a more intuitive API than Wire , with native generics support , built‑in closure capture safety that Wire lacks, and is faster than Fx by eliminating runtime reflection — all with zero runtime dependencies |
| Primary language | Go |
| License | MIT |
| Stars | 46 |
| Forks | 3 |
| Created | 2026-06-17 |
| Last push | 2026-07-28 |
| Latest release | v1.0.11 |
| Commits (last year) | 123 |
| Bus factor | 1 |
| Topics | code-generation, dependency-injection, di, dig, fx, go, golang, microservices, modular, wire, framework, wire-alternative |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| go | github.com/shanjunmei/dig | v1.0.11 | — |

## Vitality — 75/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | partial | 4.2 / 36 | 6/52 weeks with commits |
| Commit volume | met | 18 / 18 | 123 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 — 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 | 12 releases published |
| Release recency | met | 36 / 36 | latest release 10 days ago |
| Release cadence | met | 27 / 27 | a release every ~2.9 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 — 39/100 (At risk)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 26.8 / 60 | 46 stars |
| Forks | partial | 2.5 / 25 | 3 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 — 47/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) — 10/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 | not met | 0 / 10 | project has 0 contributing companies or organizations -- score normalized to 0 |

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

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

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

### Ownership & stewardship — 44/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 | not met | 0 / 25 | 0 followers of shanjunmei |
| Track record | met | 25 / 25 | 85 public repos, account ~11 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 10 days ago |
| Version history | met | 20 / 20 | 12 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

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

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

### Engineering practices — 20/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 | met | 16 / 16 | .golangci.yml |
| 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 — 60/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 | met | 10 / 10 | 12 topics |
| Wiki | met | 10 / 10 | — |

## Security — 41/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 — 26/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/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 | 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 | met | 2.5 / 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 |

### 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 3 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 — 53/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 — 40/100 (At risk)

| 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 | met | 40 / 40 | 92 of 100 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 50/100 (Moderate)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | go.mod (toolchain convention, no task runner) |
| Automated tests | not met | 0 / 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 | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | no dependencies found |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Go (statically typed) |
| Manageable file sizes | partial | 53.2 / 55 | 1/31 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 | example |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

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