open-telemetry/opentelemetry-java-instrumentation

0

/ 100

Documentation80
Engineering90
Health100
Java2,558Apache-2.01d ago
Grade a repo

A well-known project done right. Strong docs and solid engineering throughout.

OpenTelemetry auto-instrumentation and instrumentation libraries for Java

Documentation

80

Install and run instructions9pt45

README documents how to install the project.

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

90

Tests18pt80

Test files detected (benchmark-overhead/src/test).

Reproducibility6pt80

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

CI/CD14pt100

CI is configured (.github/workflows/build-common.yml).

Linting and formatting5pt100

Java/Kotlin linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (build.gradle.kts).

Repository metadata5pt100

Repository has a description.

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)
  • 1,106
    Forks
  • 122
    Releaseslatest 5y ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,558
    Watchers

Responsiveness

  • 5d 23h
    Median issue response
  • 15h
    Median PR merge time
  • 256
    Open issues
Repository files62 root entries
  • .githooks
  • .github
    Good: CI is configured (.github/workflows/build-common.yml).
    Good: Lockfile present (.github/scripts/copilot-cli/package-lock.json). Installs are reproducible.
    Good: Issue or PR templates present.
  • benchmark-jfr-analyzer
  • benchmark-overhead
    Good: Test files detected (benchmark-overhead/src/test).
  • benchmark-overhead-jmh
  • bom
  • bom-alpha
  • buildscripts
  • conventions
  • custom-checks
  • declarative-config-bridge
  • dependencyManagement
  • docs
  • examples
  • gradle
  • gradle-plugins
  • instrumentation
  • instrumentation-annotations
  • instrumentation-annotations-support
  • instrumentation-annotations-support-testing
  • instrumentation-api
  • instrumentation-api-incubator
  • instrumentation-docs
  • javaagent
  • javaagent-bootstrap
  • javaagent-extension-api
  • javaagent-internal-logging-application
  • javaagent-internal-logging-simple
  • javaagent-tooling
  • licenses
  • muzzle
  • opentelemetry-api-shaded-for-instrumenting
  • opentelemetry-ext-annotations-shaded-for-instrumenting
  • opentelemetry-instrumentation-annotations-shaded-for-instrumenting
  • opentelemetry-instrumentation-api-shaded-for-instrumenting
  • sdk-autoconfigure-support
  • smoke-tests
    Good: Environment pinned via smoke-tests/images/early-jdk8/Dockerfile.
  • smoke-tests-otel-starter
  • testing
  • testing-common
  • .clomonitor.yml
  • .editorconfig
    Good: Java/Kotlin linting configured (.editorconfig).
  • .fossa.yml
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .java-version
  • AGENTS.md
  • build.gradle.kts
    Good: Dependency manifest found (build.gradle.kts).
  • CHANGELOG.md
  • code-of-conduct.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.
  • gradle.properties
  • gradlew
  • gradlew.bat
  • ISSUES.md
  • LICENSE
    Good: Licensed under Apache-2.0.
  • mise.toml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • RELEASING.md
  • settings.gradle.kts
  • version.gradle.kts
  • VERSIONING.md