cloudwego/eino-examples

0

/ 100

Documentation64
Engineering99
Health94
Go680Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

Examples and demonstrations for using the Eino framework

Documentation

64

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

→ Add a section showing how to install dependencies.

README12pt55

README is present.

Contributing guide5pt79

Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

License6pt100

Licensed under Apache-2.0.

Engineering

99

Reproducibility6pt97

Lockfile present (go.sum). Installs are reproducible.

Tests18pt100

Test files detected (components/tool/middlewares/jsonfix/json_fix_middleware_test.go).

CI/CD14pt100

CI is configured (.github/workflows/tests.yml).

Linting and formatting5pt100

Formatting enforced (.golangci.yaml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (go.mod).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 249
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 680
    Watchers

Responsiveness

  • 1d 2h
    Median issue response
  • 1h
    Median PR merge time
  • 9
    Open issues
Repository files20 root entries
  • .github
    Good: CI is configured (.github/workflows/tests.yml).
    Good: Dependabot configured for gomod.
    Good: Issue or PR templates present.
  • adk
  • components
    Good: Test files detected (components/tool/middlewares/jsonfix/json_fix_middleware_test.go).
  • compose
  • devops
  • flow
  • internal
  • quickstart
    Good: Environment pinned via quickstart/eino_assistant/Dockerfile.
    Issue: Build artifacts or local files may be committed (quickstart/eino_assistant/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • _typos.toml
  • .gitignore
    Good: .gitignore present.
  • .golangci.yaml
    Good: Formatting enforced (.golangci.yaml).
  • .licenserc.yaml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Issue: Contributing guide is too short for full depth credit (−6 pts). 400+ words earns the full +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Good: Contributing guide describes code style expectations.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • COOKBOOK.md
  • go.mod
    Good: Dependency manifest found (go.mod).
  • go.sum
    Good: Lockfile present (go.sum). Installs are reproducible.
  • LICENSE-APACHE
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • README.zh_CN.md