httpie/cliNew scan
83/ 100 · B

Popular and well-maintained. A little polish away from elite status.

🥧 HTTPie CLI — modern, user-friendly command-line HTTP client for the API era. JSON support, colors, sessions, downloads, plugins & more.

Python38,204 starsBSD-3-Clauseupdated 1y ago
DocumentationREADME, setup, examples, license
96
EngineeringTests, CI, linting, lockfiles
78
Project healthDescription, activity, stars, deps
71

What to fix first

The highest-impact improvements for this repo.

  1. 1
    CI/CD
    EngineeringInfo

    Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.

  2. 2
    CI/CD
    EngineeringInfo

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

  3. 3
    CI/CD
    EngineeringInfo

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

Detailed breakdown

Documentation

96
  • README100
    • README is present.
    • README is well structured with multiple sections.
    • README includes screenshots or visuals. Great for first impressions.
    • README has code examples.
    • README links to a live demo or deployed app.
    • README includes status badges.
  • Install and run instructions90
    • README documents how to install the project.
    • README documents how to run the project.
    • If your project uses environment variables, add a .env.example listing them (+10 pts).Add a .env.example listing all required environment variables so contributors know what to set up.
  • License100
    • Licensed under BSD-3-Clause.
  • Contributing guide95
    • Contributing guide is detailed and thorough.
    • Contributing guide includes setup/install instructions.
    • Contributing guide lacks a code style section (−8 pts).Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
    • Contributing guide explains how to run tests.
    • Contributing guide describes the PR/review workflow.
    • Contributing guide includes code examples.
    • Code of conduct present.

Engineering

78
  • Tests90
    • Test files detected (pytest.ini).
    • Pytest configured in Python project config with test files present.
  • CI/CD85

    Not applicable?

    • CI is configured (.github/workflows/test-package-linux-snap.yml).
    • CI workflow runs tests.
    • CI runs on pull requests, not just on pushes to main.
    • CI does not appear to run a linter (−15 pts).Add a lint step (e.g. `npm run lint`, `ruff check .`, `cargo clippy`) to catch style issues automatically.
    • Optional: add type checking to CI.Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.
    • Optional: report test coverage in CI.Upload coverage to Codecov, Coveralls, or report it with `--coverage` flags.
    • CI tests across multiple environments or versions.
  • Linting and formatting60
    • Linter or formatter configured (.editorconfig).
  • Reproducibility22
    • No dependency lockfile found (−70 pts).Commit a lockfile (package-lock.json, poetry.lock, uv.lock, etc.) so installs produce the same result everywhere.
    • Environment pinned via extras/packaging/linux/Dockerfile.
    • Dependabot configured for github-actions.
    • Dependabot only covers one ecosystem (+12 pts; covering 2+ earns +20 pts).Add additional package-ecosystem entries (especially github-actions) to keep all dependencies current.
  • Issue and PR templates100
    • Issue or PR templates present.
    • Security policy present.

Project health

71
  • Dependency manifest100
    • Dependency manifest found (setup.cfg).
  • Repository metadata70
    • Repository has a description.
    • Primary language detected: Python.
  • Activity20
    • No pushes in over a year.A recent commit signals the project is alive and worth contributing to.
    • 38,204 stars.
  • Housekeeping100
    • .gitignore present.
Repository files21 root entries
  • .github
    Good: CI is configured (.github/workflows/test-package-linux-snap.yml).
    Good: Dependabot configured for github-actions.
    Good: Issue or PR templates present.
  • docs
  • extras
    Good: Environment pinned via extras/packaging/linux/Dockerfile.
  • httpie
  • tests
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .gitignore
    Good: .gitignore present.
  • .packit.yaml
  • AUTHORS.md
  • CHANGELOG.md
    Good: Contributing guide is detailed and thorough.
    Good: Contributing guide includes setup/install instructions.
    Info: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them (e.g. npm run lint, ruff check .).
    Good: Contributing guide explains how to run tests.
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
  • LICENSE
    Good: Licensed under BSD-3-Clause.
  • Makefile
  • MANIFEST.in
  • pytest.ini
    Good: Test files detected (pytest.ini).
  • 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.
  • SECURITY.md
    Good: Security policy present.
  • setup.cfg
    Good: Dependency manifest found (setup.cfg).
  • setup.py
  • snapcraft.yaml