open-telemetry/semantic-conventions-genai

0

/ 100

Documentation67
Engineering55
Health84
Python89Apache-2.01d ago
Grade a repo

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

Documentation

67

Install and run instructions9pt45

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

→ Add a section showing how to install dependencies.

README12pt65

README is present.

Contributing guide5pt72

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

55

Tests18pt0

No tests detected anywhere in the repository.

→ Add automated tests. They prove the code works and give contributors confidence to make changes.

CI/CD14pt72

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

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Reproducibility6pt100

Lockfile present (.github/scripts/copilot-cli/package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

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 (.github/scripts/copilot-cli/package.json).

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)
  • 39
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • 2d 3h
    Median issue response
  • 1h
    Median PR merge time
  • 149
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
    Good: Lockfile present (.github/scripts/copilot-cli/package-lock.json). Installs are reproducible.
    Good: Dependabot covers 2 ecosystems (uv, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: Dependency manifest found (.github/scripts/copilot-cli/package.json).
  • changelog.d
  • docs
  • model
  • reference
  • templates
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • CHANGELOG.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    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.
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • mise.toml
    Good: Environment pinned via mise.toml.
  • README.md
    Good: README is present.
    Issue: README is fairly short (−10 pts). At 400+ chars you get partial credit; 1,500+ earns the full +20 pts.Fix: Expand with a description, install steps, usage, and examples.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
  • RELEASING.md
  • versions.env