awslabs/amazon-kinesis-client

0

/ 100

Documentation89
Engineering71
Health100
Java662Apache-2.01d ago
Grade a repo

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

Client library for Amazon Kinesis

Documentation

89

Contributing guide5pt72

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

71

Reproducibility6pt20

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/run_integ_tests.yml).

Tests18pt80

Test files detected (amazon-kinesis-client-multilang/src/test).

Linting and formatting5pt100

Java/Kotlin linting configured (checkstyle/checkstyle.xml).

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)
  • 484
    Forks
  • 137
    Releaseslatest 10y ago

Community

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

Responsiveness

  • 1d 14h
    Median issue response
  • 16d 8h
    Median PR merge time
  • 335
    Open issues
Repository files17 root entries
  • .github
    Good: CI is configured (.github/workflows/run_integ_tests.yml).
    Good: Dependabot covers 3 ecosystems (maven, maven, maven). Dependencies stay current.
    Good: Issue or PR templates present.
  • amazon-kinesis-client
  • amazon-kinesis-client-multilang
    Good: Test files detected (amazon-kinesis-client-multilang/src/test).
  • checkstyle
    Good: Java/Kotlin linting configured (checkstyle/checkstyle.xml).
  • docs
  • formatter
  • META-INF
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • 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.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • NOTICE.txt
  • 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.