audreyfeldroy/cookiecutter-pypackage

Cookiecutter template for a Python package.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 15th, 2026
Created on July 14th, 2013
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 1,789
Total Stargazers: 4,601 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 113.4 days
Mean response time: 877.8 days
90th percentile: 3531.5 days
Tracked items: 82

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 199 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Please Help (14)
  • pyconlt-2024 (10)
  • High-Priority (5)
  • enhancement (4)
  • Low Hanging Fruit (2)
  • bug (2)
  • good first issue (2)
  • Waiting for Dependency Update (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Cookiecutter PyPackage is a Cookiecutter template that scaffolds a Python package with production-ready CI/CD and automated PyPI publishing.

The template solves the problem of setting up a modern Python package from scratch with all necessary tooling and infrastructure already configured. It bundles a curated stack including uv for package management, ruff for linting and formatting, pytest for testing, and Typer for CLI frameworks. The approach works by generating a complete project structure with GitHub Actions workflows pre-configured for continuous integration, security-hardened deployments to PyPI using Trusted Publishers and Sigstore attestations, and automatic documentation deployment to GitHub Pages.

Developers should choose this template if they want to start a new Python package without manually configuring linting, type checking, testing across multiple Python versions, or CI/CD pipelines. It suits projects intended for PyPI distribution and those that benefit from GitHub Pages documentation. The template is particularly valuable for teams that want security best practices built in from the start, such as SHA-pinned GitHub Actions, minimal permissions, and token-free PyPI publishing.

The project maintains active engagement with its tooling ecosystem, regularly incorporating updates to dependencies and GitHub Actions through automated Dependabot pull requests. Development activity shows responsiveness to modern Python packaging standards, as evidenced by the adoption of newer tools like uv and the implementation of security-hardened CI/CD patterns. The template receives ongoing maintenance to keep generated projects compatible with current Python versions and best practices.