tangerg/lynx
Grade a repo

0

/ 100

GradeF

Getting some notice. Tests and CI would be the fastest wins.

Higher than 39% of 5,156 graded repos
Documentation0
Engineering77
Health84
Go121mo ago

A low grade is a to-do list, not a judgment of your code

Most gaps here are documentation, tests, and setup, not the code itself. Closing your top 3 gaps alone would lift this repo to C (78).

See your top fixes
Now
F
54
Potential
C
78

Top fixes

Highest-impact changes first, ranked by point weight

13 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    README12pt

    Add a README.md describing what the project does, how to install it, and how to run it.

  3. 3
    Install and run instructions9pt

    Add a section showing how to install dependencies.

  4. 4
    Install and run instructions9pt

    Add a section showing how to start or use the project.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

0

README12pt0

No README found in the repository.

→ Add a README.md describing what the project does, how to install it, and how to run it.

Install and run instructions9pt0

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

→ Add a section showing how to install dependencies.

License6pt0

No license detected.

→ Add a LICENSE file. Without one, nobody can legally use, copy, or contribute to your code.

Contributing guide5pt0

No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).

→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.

Engineering

77

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

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

Tests18pt80

Test files detected (a2a/a2a_test.go).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.golangci.yml).

Project health

84

Repository metadata5pt40

No repository description set on GitHub (−60 pts).

→ Add a one-line description in the repo Settings → About. It appears in search results and social previews.

Dependency manifest6pt100

Dependency manifest found (go.work).

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 3
    Forks
  • 0
    Releases

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 12
    Watchers

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files24 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • a2a
    Good: Test files detected (a2a/a2a_test.go).
    Good: Lockfile present (a2a/go.sum). Installs are reproducible.
  • agent
  • app
  • chatmemory
  • core
  • doc
  • documentreaders
  • mcp
  • models
  • otel
  • pkg
  • rag
  • scripts
  • skills
  • tools
  • vectorstores
  • .gitignore
    Good: .gitignore present.
  • .golangci.yml
    Good: Linter or formatter configured (.golangci.yml).
  • CLAUDE.md
  • DESIGN_PHILOSOPHY.md
  • go.work
    Good: Dependency manifest found (go.work).
  • go.work.sum
  • REFACTORING.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/tangerg/lynx)](https://www.repo-grade.com/report/tangerg/lynx)

More graded Go repos