karrioapi/karrio
Grade a repo

78

/ 100

GradeC

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

Top 35% of 5,156 graded repos

Programmable Shipping APIs (self-hosted)

Documentation96
Engineering65
Health83
Python738Other1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    CI/CD14pt

    Add `pull_request:` to the workflow `on:` triggers.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

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

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

96

Contributing guide5pt77

CONTRIBUTING guide found.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Other.

Engineering

65

Tests18pt35

Test files detected (apps/api/karrio/server/test_runner.py).

CI/CD14pt68

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

Reproducibility6pt80

Lockfile present (package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

83

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt65

Dependency manifest found (package.json).

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

  • 1 / 28
    Commits (30d / 90d)
  • 176
    Forks
  • 239
    Releaseslatest 7y ago

Community

  • 87% - Good
    Community health
  • 1 bus factorlow
    author own >50% of commits
  • 738
    Watchers

Responsiveness

  • -
    Median issue response
  • <1h
    Median PR merge time
  • 77
    Open issues
Repository files61 root entries
  • .claude
  • .cursor
  • .github
    Good: CI is configured (.github/workflows/build.yml).
    Good: Issue or PR templates present.
  • .postman
  • .vscode
  • apps
    Good: CONTRIBUTING guide found.
    Issue: CONTRIBUTING guide contents could not be read (−28 pts vs a readable file).Fix: Move the file to the repo root or docs/CONTRIBUTING.md so its setup, style, test, and PR sections can be graded.
    Good: Test files detected (apps/api/karrio/server/test_runner.py).
  • bin
  • carrier-testing
  • charts
  • docker
    Issue: Build artifacts or local files may be committed (docker/.env) (−40 pts).Fix: Remove them and add to .gitignore.
  • docs
  • ee
  • modules
  • packages
  • plugins
  • postman
  • PRDs
  • schemas
  • screenshots
  • specs
  • .coveragerc
  • .cursorignore
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.sample
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .npmrc
  • AGENTS.md
  • CARRIER_INTEGRATION_FAQ.md
  • CARRIER_INTEGRATION_GUIDE.md
  • CARRIER_INTEGRATION_PROMPT_TEMPLATE.md
  • CHANGELOG.md
  • CLAUDE.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CODEX.md
  • community
  • docker-compose.yml
    Good: Environment pinned via docker-compose.yml.
  • GEMINI.md
  • LICENSE
    Good: Licensed under Other.
  • LICENSE_EE
  • mypy.ini
  • openapitools.json
  • package-lock.json
    Good: Lockfile present (package-lock.json). Installs are reproducible.
  • package.json
    Good: Dependency manifest found (package.json).
  • 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.
  • requirements.build.insiders.txt
  • requirements.build.platform.txt
  • requirements.build.txt
  • requirements.dev.txt
  • requirements.insiders.dev.txt
  • requirements.insiders.txt
  • requirements.platform.dev.txt
  • requirements.platform.txt
  • requirements.sdk.dev.txt
  • requirements.server.dev.txt
  • requirements.txt
  • SECURITY.md
    Good: Security policy present.
  • source.requirements.insiders.txt
  • source.requirements.platform.txt
  • source.requirements.txt
  • turbo.json
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/karrioapi/karrio)](https://www.repo-grade.com/report/karrioapi/karrio)

More graded Python repos