ibm/lale
Grade a repo

0

/ 100

GradeB

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

Top 30% of 5,156 graded repos

Library for Semi-Automated Data Science

Documentation83
Engineering78
Health88
Python347Apache-2.01mo ago

Top fixes

Highest-impact changes first, ranked by point weight

17 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
    README12pt

    Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.

  3. 3
    README12pt

    Show a quick-start snippet so contributors can see what using your project looks like.

  4. 4
    Install and run instructions9pt

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

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

83

README12pt70

README is present.

Contributing guide5pt79

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

78

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Tests18pt80

Test files detected (test).

Reproducibility6pt80

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

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (.flake8).

Project health

88

Dependency manifest6pt62

Dependency manifest found (pyproject.toml).

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)
  • 83
    Forks
  • 88
    Releaseslatest 6y ago

Community

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

Responsiveness

  • 2d 8h
    Median issue response
  • 2h
    Median PR merge time
  • 24
    Open issues
Repository files24 root entries
  • .github
    Good: CI is configured (.github/workflows/build.yml).
  • docs
    Good: Lockfile present (docs/requirements.txt). Installs are reproducible.
  • examples
  • lale
  • talks
  • test
    Good: Test files detected (test).
  • .flake8
    Good: Linter or formatter configured (.flake8).
  • .gitignore
    Good: .gitignore present.
  • .isort.cfg
  • .pre-commit-config.yaml
  • .readthedocs.yml
  • .yamllint
  • bandit.yaml
  • CONTRIBUTING.md
    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.
    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.
  • DCO1.1.txt
  • Dockerfile
    Good: Environment pinned via Dockerfile.
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • Makefile
  • mypy.ini
  • pylintrc
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • pyrightconfig.json
  • README.md
    Good: README is present.
    Issue: README has little structure (−15 pts). Add 2-3 headings for +8 pts; 4+ earns +15 pts.Fix: Break it into sections (Overview, Install, Usage, Contributing) using Markdown headings.
    Good: README includes screenshots or visuals. Great for first impressions.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    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.
  • setup.py
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/ibm/lale)](https://www.repo-grade.com/report/ibm/lale)

More graded Python repos