Awesome-Claude-Code Dependencies: Runtime and Development Requirements Explained

The awesome-claude-code project requires two runtime dependencies (PyGithub and PyYAML) and ten development dependencies including pytest, mypy, and ruff, all declared in pyproject.toml.

The hesreallyhim/awesome-claude-code repository is a curated automation tool that manages GitHub API interactions and YAML processing. Understanding its dependency structure is essential for contributors and users who want to install the package correctly or extend its functionality. The project uses modern Python packaging standards with all requirements explicitly pinned in the pyproject.toml file.

Runtime Dependencies

The core functionality of awesome-claude-code relies on two external libraries defined in [project.dependencies] at line 13 of pyproject.toml.

PyGithub (>=2.1.1)

PyGithub serves as the GitHub API client wrapper. The project uses this library in scripts/utils/github_utils.py to authenticate with the GitHub API, fetch repository metadata, and manage rate limiting. Version 2.1.1 or higher ensures compatibility with recent GitHub API changes and security patches.

PyYAML (>=6.0.0)

PyYAML handles all YAML parsing and serialization tasks. This dependency supports reading configuration files and generating structured data outputs. The minimum version constraint of 6.0.0 provides critical security fixes and improved C-based loader performance.

Development Dependencies

Contributors and maintainers need additional tooling defined in the [project.optional-dependencies] section starting at line 25 of pyproject.toml. These packages are not required for end-users but enable testing, linting, and type checking.

Testing and Coverage Tools

• pytest (>=8.0.0) – The primary test runner for executing unit tests in the tests/ directory
• pytest-cov (>=7.0.0) – Generates coverage reports to ensure code quality standards
• requests (>=2.31.0) – HTTP client library used by the test suite to mock API calls

Type Safety and Linting

• mypy (>=1.10.0) – Static type checker that validates type hints across the codebase
• ruff (>=0.1.0) – Fast Python linter and code formatter replacing flake8 and black
• types-requests (>=2.31.0) and types-PyYAML (>=6.0.0) – Type stub packages enabling mypy to check external library usage

Development Workflow

• python-dotenv (>=1.0.0) – Loads environment variables from .env files during local development
• pre-commit (>=3.5.0) – Manages git hooks to enforce code quality checks before commits

Installing the Dependencies

Install only the runtime requirements for basic usage:

pip install "PyGithub>=2.1.1" "PyYAML>=6.0.0"

For development work including testing and linting, install the package in editable mode with development extras:

pip install -e .[dev]

This command reads the pyproject.toml and installs all ten development dependencies alongside the runtime requirements.

How Dependencies Are Used in the Source Code

The dependency declarations directly correspond to implementation details in specific source files.

In scripts/utils/github_utils.py, the code imports from github (PyGithub) to create authenticated GitHub clients and handle repository queries. The tests/test_github_utils.py file imports pytest and requests to validate this functionality through mocked HTTP interactions.

The pyproject.toml file at the repository root serves as the single source of truth. Line 13 declares the runtime constraints, while lines 25-33 enumerate the development toolchain. This structure follows PEP 621 standards for modern Python packaging.

Summary

• awesome-claude-code declares dependencies exclusively in pyproject.toml following modern Python standards
• Runtime requirements are limited to PyGithub (>=2.1.1) and PyYAML (>=6.0.0) for GitHub API and YAML operations
• Development requirements include pytest, mypy, ruff, and six additional tools for testing and code quality
• Install production dependencies with standard pip commands, or use pip install -e .[dev] for full development setup
• The scripts/utils/github_utils.py file demonstrates PyGithub usage, while the tests/ directory exercises the pytest and requests dependencies

Frequently Asked Questions

What Python version is required for awesome-claude-code dependencies?

The pyproject.toml specifies Python 3.8 or higher in its classifiers and build system requirements. All declared dependencies (PyGithub 2.1.1+ and PyYAML 6.0.0+) maintain compatibility with Python 3.8 through 3.12, ensuring broad environment support while using modern language features.

Can I run the test suite without installing all development dependencies?

No, running pytest requires the full development installation. The test suite in the tests/ directory imports pytest, requests, and python-dotenv directly. Attempting to run tests without these packages installed will result in ModuleNotFoundError exceptions when the test collector imports the test files.

Why does the project use both PyGithub and requests?

PyGithub handles the main runtime GitHub API interactions with proper object modeling and authentication, while requests appears only in the development dependencies. The test suite uses requests to mock HTTP responses and validate error handling without making live API calls, keeping tests fast and deterministic.

How are dependency updates managed in awesome-claude-code?

The project uses pre-commit hooks (declared at line 31 of pyproject.toml) and ruff (line 30) to validate code against updated dependency APIs. The >= version constraints allow patch and minor updates while preventing breaking changes. Contributors should run the full test suite with pytest after any dependency upgrade to ensure compatibility with scripts/utils/github_utils.py and other core modules.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}