javachengwc/util
Grade a repo

0

/ 100

GradeB

Solid engineering. The main gap is visibility.

Top 26% of 5,156 graded repos

Wonderful reusable code from Twitter

Documentation94
Engineering79
Health75
Scala0Apache-2.08y 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
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  3. 3
    Reproducibility6pt

    Add a Dockerfile, .nvmrc, or .python-version to pin the runtime version and make the environment reproducible.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

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

94

Contributing guide5pt80

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

README12pt100

README is present.

License6pt100

Licensed under Apache-2.0.

Engineering

79

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.

Reproducibility6pt70

Lockfile present (codegen/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (util-app/src/test).

CI/CD14pt100

CI is configured (.travis.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

75

Activity5pt5

No pushes in over 2 years. Looks unmaintained (−95 pts).

→ A recent commit signals the project is alive and worth using.

Dependency manifest6pt100

Dependency manifest found (codegen/requirements.txt).

Repository metadata5pt100

Repository has a description.

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 0
    Forks
  • 0
    Releases

Community

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

Responsiveness

  • -
    Median issue response
  • -
    Median PR merge time
  • 0
    Open issues
Repository files41 root entries
  • .github
    Good: Issue or PR templates present.
  • codegen
    Good: Lockfile present (codegen/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (codegen/requirements.txt).
  • doc
  • project
  • site
  • util-app
    Good: Test files detected (util-app/src/test).
  • util-benchmark
  • util-cache
  • util-class-preloader
  • util-codec
  • util-collection
  • util-core
  • util-function
  • util-hashing
  • util-jvm
  • util-lint
  • util-logging
  • util-reflect
  • util-registry
  • util-security
  • util-slf4j-api
  • util-slf4j-jul-bridge
  • util-stats
  • util-test
  • util-thrift
  • util-tunable
  • util-zk
  • util-zk-test
  • .gitignore
    Good: .gitignore present.
  • .travis.yml
    Good: CI is configured (.travis.yml).
  • build.sbt
  • CHANGES
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONFIG.ini
  • 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.
    Good: Contributing guide explains how to run tests.
    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.
  • GROUPS
  • LICENSE
    Good: Licensed under Apache-2.0.
  • OWNERS
  • pushsite.bash
  • 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.
    Good: README documents how to run the project.
  • sbt
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/javachengwc/util)](https://www.repo-grade.com/report/javachengwc/util)

More graded Scala repos