apache/pekko
Grade a repo

0

/ 100

GradeC

Good community traction and solid fundamentals. Nearly in the top tier.

Build highly concurrent, distributed, and resilient message-driven applications using Java/Scala

Documentation89
Engineering59
Health68
Scala1,594Apache-2.0today

Documentation

89

Contributing guide5pt84

Contributing guide is detailed and thorough.

README12pt85

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

59

Linting and formatting5pt0

No linter or formatter config found.

→ Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Reproducibility6pt12

No dependency lockfile found (−70 pts).

→ Commit the lockfile for this project's package manager so installs produce the same dependency versions everywhere.

CI/CD14pt57

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

Tests18pt80

Test files detected (actor-testkit-typed/src/test).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

68

Dependency manifest6pt0

No dependency manifest detected at root.

→ Add a manifest (package.json, pyproject.toml, Cargo.toml, go.mod, etc.) so others can install dependencies in one command.

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

Community

  • -
    Community health
  • -
    authors own >50% of commits
  • 1,594
    Watchers

Responsiveness

  • 15h
    Median issue response
  • 14h
    Median PR merge time
  • 236
    Open issues
Repository files63 root entries
  • .github
    Good: CI is configured (.github/workflows/build-test-prValidation.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • actor
  • actor-testkit-typed
    Good: Test files detected (actor-testkit-typed/src/test).
  • actor-tests
  • actor-typed
  • actor-typed-tests
  • bench-jmh
  • cluster
  • cluster-metrics
  • cluster-sharding
  • cluster-sharding-typed
  • cluster-tools
  • cluster-typed
  • coordination
  • discovery
  • distributed-data
  • docs
  • kubernetes
  • legal
  • multi-node-testkit
  • osgi
  • persistence
  • persistence-query
  • persistence-shared
  • persistence-tck
  • persistence-testkit
  • persistence-typed
  • persistence-typed-tests
  • pki
  • project
  • remote
  • remote-tests
  • scripts
  • serialization-jackson
  • serialization-jackson3
  • slf4j
  • stream
  • stream-testkit
  • stream-tests
  • stream-tests-tck
  • stream-typed
  • stream-typed-tests
  • testkit
  • .asf.yaml
  • .git-blame-ignore-revs
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .jvmopts-ci
  • .sbt-java-formatter.conf
  • .sbtopts
  • .scala-steward.conf
  • .scalafix.conf
  • .scalafmt.conf
  • AGENTS.md
  • build.sbt
  • CHANGELOG.md
  • CLAUDE.md
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    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.
  • COPYING.protobuf
  • KEYS
  • LICENSE
    Good: Licensed under Apache-2.0.
  • NOTICE
  • README.md
    Good: README is present.
    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.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.