0

/ 100

GradeB

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

Top 26% of 5,156 graded repos

A collection of Java libraries for connecting securely to Cloud SQL

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

    Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.

  4. 4
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

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

71

Install and run instructions9pt45

No install instructions found in the README (−45 pts).

Add a section showing how to install dependencies.

README12pt70

README is present.

Contributing guide5pt85

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

85

CI/CD14pt72

CI is configured (.github/workflows/lint.yaml).

Tests18pt80

Test files detected (core/src/test).

Linting and formatting5pt100

Java/Kotlin linting configured (lint step in CI workflow).

Reproducibility6pt100

Lockfile present (.kokoro/requirements.txt). 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)
  • 117
    Forks
  • 81
    Releaseslatest 5y ago

Community

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

Responsiveness

  • 11h
    Median issue response
  • 2h
    Median PR merge time
  • 42
    Open issues
Repository files30 root entries
  • .ci
  • .github
    Good: CI is configured (.github/workflows/lint.yaml).
    Good: Dependabot covers 2 ecosystems (maven, pip). Dependencies stay current.
    Good: Issue or PR templates present.
  • .kokoro
    Good: Lockfile present (.kokoro/requirements.txt). Installs are reproducible.
  • .mvn
  • .release
  • core
    Good: Test files detected (core/src/test).
  • docs
  • examples
    Good: Environment pinned via examples/cloudrun/mariadb/Dockerfile.
  • jdbc
  • r2dbc
  • schemas
  • .envrc.example
  • .gitignore
    Good: .gitignore present.
  • .repo-metadata.json
  • build.sh
  • CHANGELOG.md
  • checkstyle-suppressions.xml
  • 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.
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • gitignore
  • java.header
  • LICENSE
    Good: Licensed under Apache-2.0.
  • license-checks.xml
  • mvnw
  • mvnw.cmd
  • owlbot.py
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    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.
    Issue: No install instructions found in the README (−45 pts).Fix: Add a section showing how to install dependencies.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • versions.txt
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/googlecloudplatform/cloud-sql-jdbc-socket-factory)](https://www.repo-grade.com/report/googlecloudplatform/cloud-sql-jdbc-socket-factory)

More graded Java repos