aklivity/zilla
Grade a repo

0

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 28% of 5,156 graded repos

🦎 A multi-protocol edge & service proxy. Seamlessly interface web apps, IoT clients, & microservices to Apache Kafka® via declaratively defined, stateless APIs.

Documentation90
Engineering70
Health100
Java691Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 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
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

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

90

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

70

Linting and formatting5pt0

No Java/Kotlin linter configured.

→ Add Checkstyle or Spotless for Java formatting, or ktlint/Detekt for Kotlin. Run it via Maven/Gradle or as a CI step.

CI/CD14pt57

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

Tests18pt80

Test files detected (build/flyweight-maven-plugin/src/test).

Reproducibility6pt100

Lockfile present (examples/mcp.proxy/url-elicit/package-lock.json). Installs are reproducible.

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 71
    Forks
  • 68
    Releaseslatest 2y ago

Community

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

Responsiveness

  • 8h
    Median issue response
  • <1h
    Median PR merge time
  • 220
    Open issues
Repository files28 root entries
  • .github
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Code of conduct present.
    Good: CI is configured (.github/workflows/build.yml).
    Good: Dependabot covers 3 ecosystems (maven, docker, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • .mvn
  • assets
  • build
    Good: Test files detected (build/flyweight-maven-plugin/src/test).
  • cloud
    Good: Environment pinned via cloud/docker-image/src/main/docker/Dockerfile.
  • conf
  • examples
    Good: Lockfile present (examples/mcp.proxy/url-elicit/package-lock.json). Installs are reproducible.
  • incubator
  • manager
  • runtime
  • specs
  • .github_changelog_generator
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CHANGELOG.md
  • CLAUDE.md
  • COPYRIGHT-AklivityCommunity
  • COPYRIGHT-Apache
  • LICENSE
    Good: Licensed under Other.
  • LICENSE-AklivityCommunity
  • LICENSE-Apache
  • mvnw
  • mvnw.cmd
  • NOTICE-AklivityCommunity
  • NOTICE-Apache
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
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/aklivity/zilla)](https://www.repo-grade.com/report/aklivity/zilla)

More graded Java repos