datajunction/dj
Grade a repo

0

/ 100

GradeB

Polished and well engineered. Punching above its star count.

Top 16% of 5,156 graded repos

A metrics platform.

Documentation86
Engineering90
Health85
Python155MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

10 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 section showing how to start or use the project.

  3. 3
    Reproducibility6pt

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

  4. 4
    Dependency manifest6pt

    Add `description = "..."` under [project]. It shows on PyPI and in tooling.

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

86

Install and run instructions9pt55

README documents how to install the project.

Contributing guide5pt89

Contributing guide is detailed and thorough.

README12pt100

README is present.

License6pt100

Licensed under MIT.

Engineering

90

Tests18pt80

Test files detected (datajunction-clients/java/src/test).

Reproducibility6pt80

Lockfile present (uv.lock). Installs are reproducible.

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (datajunction-clients/javascript/.eslintrc.js).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

85

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt71

Dependency manifest found (pyproject.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 29
    Forks
  • 161
    Releaseslatest 6mo ago

Community

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

Responsiveness

  • 11h
    Median issue response
  • <1h
    Median PR merge time
  • 305
    Open issues
Repository files28 root entries
  • .github
    Good: CI is configured (.github/workflows/test.yml).
    Good: Issue or PR templates present.
  • datajunction-clients
    Good: Test files detected (datajunction-clients/java/src/test).
    Good: Linter or formatter configured (datajunction-clients/javascript/.eslintrc.js).
  • datajunction-query
    Good: Environment pinned via datajunction-query/Dockerfile.
  • datajunction-reflection
  • datajunction-server
    Issue: Build artifacts or local files may be committed (datajunction-server/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • datajunction-ui
  • db-init
  • docs
  • notebooks
  • talks
  • tpcds
  • .coveragerc
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .pre-commit-config.yaml
  • AUTHORS.rst
  • CHANGELOG.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.rst
    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.
    Good: Contributing guide explains how to run tests.
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Good: Contributing guide includes code examples.
  • dev.sh
  • docker-compose.yml
  • LICENSE.txt
    Good: Licensed under MIT.
  • netlify.toml
  • openapi.json
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • 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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • tox.ini
  • uv.lock
    Good: Lockfile present (uv.lock). Installs are reproducible.
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/datajunction/dj)](https://www.repo-grade.com/report/datajunction/dj)

More graded Python repos