boto/botocore

0

/ 100

Documentation73
Engineering91
Health86
Python1,625Apache-2.01d ago
Grade a repo

Good community traction and solid fundamentals. Nearly in the top tier.

The low-level, core functionality of boto3 and the AWS CLI.

Documentation

73

README12pt40

README is present.

Install and run instructions9pt90

README documents how to install the project.

Contributing guide5pt92

Contributing guide is detailed and thorough.

License6pt100

Licensed under Apache-2.0.

Engineering

91

CI/CD14pt72

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

Reproducibility6pt90

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

Tests18pt100

Test files detected (tests).

Linting and formatting5pt100

Linter or formatter configured ([tool.ruff] / [tool.black] in pyproject.toml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

86

Dependency manifest6pt55

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)
  • 1,164
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 1,625
    Watchers

Responsiveness

  • <1h
    Median issue response
  • 3h
    Median PR merge time
  • 174
    Open issues
Repository files27 root entries
  • .changes
  • .github
    Good: CI is configured (.github/workflows/lint.yml).
    Good: Dependabot covers 2 ecosystems (github-actions, pre-commit). Dependencies stay current.
    Good: Issue or PR templates present.
    Good: Security policy present.
  • botocore
  • docs
  • scripts
  • tests
    Good: Test files detected (tests).
  • .codecov.yml
  • .coveragerc
  • .git-blame-ignore-revs
  • .gitignore
    Good: .gitignore present.
  • .pre-commit-config.yaml
  • CHANGELOG.rst
  • 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.
    Good: Contributing guide describes code style expectations.
    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.
  • LICENSE.txt
    Good: Licensed under Apache-2.0.
  • MANIFEST.in
  • NOTICE
  • pyproject.toml
    Good: Dependency manifest found (pyproject.toml).
  • README.rst
    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.
    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.
    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.
    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.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • requirements-dev-lock.txt
  • requirements-dev.txt
  • requirements-docs-lock.txt
  • requirements-docs.txt
  • requirements.txt
    Good: Lockfile present (requirements.txt). Installs are reproducible.
  • setup.cfg
  • setup.py
  • tox.ini