pygenkit 0.2.0__tar.gz → 0.2.4__tar.gz

{pygenkit-0.2.0/src/pygenkit.egg-info → pygenkit-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pygenkit
-Version: 0.2.0
+Version: 0.2.4
 Summary: Professional Python project generator — PyPI, APT, and Launchpad ready
 Author-email: Alan Santos <alan.profissional.dev@gmail.com>
 License-Expression: GPL-3.0-only
@@ -17,10 +17,33 @@ Dynamic: license-file
 
 # PyGenKit
 
+[![CI](https://github.com/alan-n7x/pygenkit/actions/workflows/ci.yml/badge.svg)](https://github.com/alan-n7x/pygenkit/actions/workflows/ci.yml)
+[![Python](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://www.python.org/)
+[![License: GPL v3](https://img.shields.io/badge/license-GPL--3.0--only-blue.svg)](LICENSE)
+[![Code style: Ruff](https://img.shields.io/badge/code%20style-ruff-blue.svg)](https://docs.astral.sh/ruff/)
+[![Typing: MyPy](https://img.shields.io/badge/typing-mypy-blue.svg)](https://mypy-lang.org/)
+
 Professional Python project generator -- **PyPI**, **APT**, and **Launchpad** ready.
 
-Inspect existing Python projects, validate version consistency and CI/CD security, and
-generate GitHub Actions pipelines, Dockerfiles, and deploy configs.
+PyGenKit helps you bootstrap, inspect, validate, and release Python projects with a production-oriented workflow. It can analyze an existing codebase, check version consistency and CI/CD security, and generate GitHub Actions pipelines, Dockerfiles, and deploy configuration files.
+
+<p align="center">
+  <img src="docs/demo.svg" alt="PyGenKit terminal demo" width="900">
+</p>
+
+## Why PyGenKit?
+
+Modern Python projects often need more than just source code: packaging metadata, CI, linting, type checking, tests, release automation, Docker, and deployment files. PyGenKit brings those pieces together in a repeatable CLI workflow so new projects start with a professional foundation.
+
+## Features
+
+- Scaffold Python projects with a `src/` layout and CI/CD-ready defaults
+- Inspect existing projects for metadata, packaging, versioning, and workflow state
+- Validate version consistency across project files, git tags, and Debian packaging files
+- Detect risky CI/CD patterns, outdated actions, missing permissions, and potential secrets
+- Generate GitHub Actions workflows for CI, releases, PyPI, and Launchpad publishing
+- Generate Docker and deployment configuration for common platforms
+- Check local development requirements with a `doctor` command
 
 ## Installation
 
@@ -44,28 +67,40 @@ cd my-app
 # Inspect project structure
 pygenkit inspect
 
-# Validate versions, workflows, security
+# Validate versions, workflows, and security
 pygenkit validate
 
-# Generate CI/CD pipelines, Docker, deploy configs
+# Generate CI/CD pipelines, Docker, and deploy configs
 pygenkit generate
 
 # Check system requirements
 pygenkit doctor
 ```
 
+## Example Output
+
+```text
+Project: my-app
+Version: 0.1.0
+Python: >=3.12
+Build backend: setuptools
+License: MIT
+CI/CD: GitHub Actions detected
+Status: ready for validation
+```
+
 ## Commands
 
 | Command         | Description                                    |
 |-----------------|------------------------------------------------|
 | `new`           | Scaffold a complete Python project with CI/CD  |
-| `init`          | Create `pygenkit.toml` in an existing project |
+| `init`          | Create `pygenkit.toml` in an existing project  |
 | `inspect`       | Analyze project structure, versions, metadata  |
 | `validate`      | Check version consistency, workflows, security |
 | `generate`      | Generate CI/CD, Docker, and deploy files       |
 | `health`        | Assess project health across 7 categories      |
 | `review`        | Review a GitHub PR diff using AI               |
-| `release-check` | Verify release readiness (coming soon)         |
+| `release-check` | Verify release readiness before tagging        |
 | `doctor`        | Check system for required tools                |
 
 ## Usage
@@ -77,7 +112,7 @@ pygenkit init my-project
 # Inspect project
 pygenkit inspect
 
-# Validate
+# Validate project metadata, workflows, and security
 pygenkit validate
 
 # Generate GitHub Actions CI/CD pipelines
@@ -107,9 +142,9 @@ pygenkit generate --force
 Scans your project and reports:
 
 - Project name, version, module
-- Build backend (setuptools, hatchling, poetry, etc.)
+- Build backend: setuptools, hatchling, poetry, etc.
 - Python version requirement
-- License type (MIT, Apache, GPL, etc.)
+- License type: MIT, Apache, GPL, etc.
 - Version consistency between `pyproject.toml`, `__init__.py`, `debian/changelog`, and git tags
 - CI/CD workflow detection
 - Debian packaging status
@@ -118,37 +153,37 @@ Scans your project and reports:
 
 Runs three categories of checks:
 
-- **Version**: consistency across `pyproject.toml`, `__init__.py`, `debian/changelog`, git tags
-- **Workflow**: YAML validity, missing metadata, outdated actions (`checkout@v3`), SHA pin warnings, script injection
-- **Security**: missing permissions blocks, hardcoded secrets, PyPI publish without protected environment
+- **Version**: consistency across `pyproject.toml`, `__init__.py`, `debian/changelog`, and git tags
+- **Workflow**: YAML validity, missing metadata, outdated actions, SHA pin warnings, and script injection risks
+- **Security**: missing permissions blocks, hardcoded secrets, and PyPI publishing without a protected environment
 
 ## Generate
 
-Generates files from Jinja2 templates based on `pygenkit.toml`:
+Generates files from Jinja2 templates based on `pygenkit.toml`.
 
 ### GitHub Actions
 
-| File                   | Description                               |
-|------------------------|-------------------------------------------|
-| `.github/workflows/ci.yml` | Ruff lint, MyPy type-check, Pytest      |
-| `.github/workflows/release.yml` | Build wheel, create GitHub Release |
-| `.github/workflows/publish-pypi.yml` | Trusted PyPI publishing     |
-| `.github/workflows/publish-launchpad.yml` | dput to Launchpad PPA   |
+| File                                      | Description                          |
+|-------------------------------------------|--------------------------------------|
+| `.github/workflows/ci.yml`                | Ruff lint, MyPy type-check, Pytest   |
+| `.github/workflows/release.yml`           | Build wheel and create GitHub Release |
+| `.github/workflows/publish-pypi.yml`      | Trusted PyPI publishing              |
+| `.github/workflows/publish-launchpad.yml` | dput to Launchpad PPA                |
 
 ### Docker
 
-| File                 | Description            |
-|----------------------|------------------------|
-| `Dockerfile`         | Multi-stage build      |
-| `docker-compose.yml` | Service configuration  |
+| File                 | Description           |
+|----------------------|-----------------------|
+| `Dockerfile`         | Multi-stage build     |
+| `docker-compose.yml` | Service configuration |
 
 ### Deploy
 
-| File            | Platform |
-|-----------------|----------|
-| `fly.toml`      | Fly.io   |
-| `Procfile`      | Heroku   |
-| `railway.json`  | Railway  |
+| File           | Platform |
+|----------------|----------|
+| `fly.toml`     | Fly.io   |
+| `Procfile`     | Heroku   |
+| `railway.json` | Railway  |
 
 ## Configuration (`pygenkit.toml`)
 
@@ -214,9 +249,10 @@ pygenkit doctor
 ```
 
 Checks for:
+
 - Python 3.12+
 - Git
-- GitHub CLI (gh)
+- GitHub CLI (`gh`)
 - GPG
 - dput
 - debhelper
@@ -225,13 +261,9 @@ Checks for:
 
 ## Publishing setup
 
-PyPI publishing uses Trusted Publishing (OIDC), so it does not require a long-lived API
-token. Configure the `pypi` environment on GitHub and authorize `release.yml` as a
-Trusted Publisher for the `pygenkit` project on PyPI. Set the repository variable
-`PYPI_ENABLED=true` to enable the publish step.
+PyPI publishing uses Trusted Publishing (OIDC), so it does not require a long-lived API token. Configure the `pypi` environment on GitHub and authorize `release.yml` as a Trusted Publisher for the `pygenkit` project on PyPI. Set the repository variable `PYPI_ENABLED=true` to enable the publish step.
 
-Launchpad publishing requires a PPA and an OpenPGP key registered with the Launchpad
-account. Add these secrets to the `launchpad` GitHub environment:
+Launchpad publishing requires a PPA and an OpenPGP key registered with the Launchpad account. Add these secrets to the `launchpad` GitHub environment:
 
 - `GPG_PRIVATE_KEY`
 - `GPG_PASSPHRASE`
@@ -239,7 +271,7 @@ account. Add these secrets to the `launchpad` GitHub environment:
 
 ## Architecture
 
-```
+```text
 src/pygenkit/
 ├── cli/              # CLI commands (Typer)
 │   └── commands/     # init, inspect, validate, generate, release-check, doctor
@@ -275,7 +307,7 @@ src/pygenkit/
 
 PyGenKit itself follows the professional workflow it generates for other projects.
 
-```
+```text
 feature branch → Pull Request → CI checks → merge to main → tag → release
 ```
 
@@ -305,33 +337,33 @@ git push origin v0.x.x     # triggers Release workflow
 
 ### Branch naming
 
-| Prefix     | Purpose                |
-|------------|------------------------|
-| `feat/*`   | New features           |
-| `fix/*`    | Bug fixes              |
-| `refactor/*` | Code improvements    |
-| `docs/*`   | Documentation          |
-| `ci/*`     | CI/CD changes          |
+| Prefix       | Purpose            |
+|--------------|--------------------|
+| `feat/*`     | New features       |
+| `fix/*`      | Bug fixes          |
+| `refactor/*` | Code improvements  |
+| `docs/*`     | Documentation      |
+| `ci/*`       | CI/CD changes      |
 
 ## Branch Protection
 
-The `main` branch **must be protected** in the GitHub repository settings:
+The `main` branch should be protected in the GitHub repository settings.
 
 ### Required settings
 
-| Setting                          | Solo | Team |
-|----------------------------------|------|------|
-| Require pull request before merging | Yes | Yes |
-| Require status checks to pass (CI)  | Yes | Yes |
-| Block force pushes                   | Yes | Yes |
-| Restrict deletions                   | Yes | Yes |
+| Setting                             | Solo | Team |
+|-------------------------------------|------|------|
+| Require pull request before merging | Yes  | Yes  |
+| Require status checks to pass       | Yes  | Yes  |
+| Block force pushes                  | Yes  | Yes  |
+| Restrict deletions                  | Yes  | Yes  |
 | Required approvals                  | 0    | 1    |
 
 When working alone, skip approval requirements. When adding maintainers, set **Required approvals: 1**.
 
 ### How to configure
 
-```
+```text
 GitHub repo → Settings → Branches → Add branch protection rule
   Branch name pattern: main
   ☑ Require a pull request before merging
@@ -341,6 +373,15 @@ GitHub repo → Settings → Branches → Add branch protection rule
   ☑ Restrict deletions
 ```
 
+## Roadmap
+
+- Add richer CLI examples and screenshots
+- Add code coverage reporting
+- Add project templates for FastAPI, CLI tools, and libraries
+- Add semantic versioning helpers
+- Add optional plugin support for custom generators
+- Expand release checks for PyPI, Debian, and Launchpad workflows
+
 ## Requirements
 
 - Python 3.12+

{pygenkit-0.2.0 → pygenkit-0.2.4}/README.md

@@ -1,9 +1,32 @@
 # PyGenKit
 
+[![CI](https://github.com/alan-n7x/pygenkit/actions/workflows/ci.yml/badge.svg)](https://github.com/alan-n7x/pygenkit/actions/workflows/ci.yml)
+[![Python](https://img.shields.io/badge/python-3.12%2B-blue.svg)](https://www.python.org/)
+[![License: GPL v3](https://img.shields.io/badge/license-GPL--3.0--only-blue.svg)](LICENSE)
+[![Code style: Ruff](https://img.shields.io/badge/code%20style-ruff-blue.svg)](https://docs.astral.sh/ruff/)
+[![Typing: MyPy](https://img.shields.io/badge/typing-mypy-blue.svg)](https://mypy-lang.org/)
+
 Professional Python project generator -- **PyPI**, **APT**, and **Launchpad** ready.
 
-Inspect existing Python projects, validate version consistency and CI/CD security, and
-generate GitHub Actions pipelines, Dockerfiles, and deploy configs.
+PyGenKit helps you bootstrap, inspect, validate, and release Python projects with a production-oriented workflow. It can analyze an existing codebase, check version consistency and CI/CD security, and generate GitHub Actions pipelines, Dockerfiles, and deploy configuration files.
+
+<p align="center">
+  <img src="docs/demo.svg" alt="PyGenKit terminal demo" width="900">
+</p>
+
+## Why PyGenKit?
+
+Modern Python projects often need more than just source code: packaging metadata, CI, linting, type checking, tests, release automation, Docker, and deployment files. PyGenKit brings those pieces together in a repeatable CLI workflow so new projects start with a professional foundation.
+
+## Features
+
+- Scaffold Python projects with a `src/` layout and CI/CD-ready defaults
+- Inspect existing projects for metadata, packaging, versioning, and workflow state
+- Validate version consistency across project files, git tags, and Debian packaging files
+- Detect risky CI/CD patterns, outdated actions, missing permissions, and potential secrets
+- Generate GitHub Actions workflows for CI, releases, PyPI, and Launchpad publishing
+- Generate Docker and deployment configuration for common platforms
+- Check local development requirements with a `doctor` command
 
 ## Installation
 
@@ -27,28 +50,40 @@ cd my-app
 # Inspect project structure
 pygenkit inspect
 
-# Validate versions, workflows, security
+# Validate versions, workflows, and security
 pygenkit validate
 
-# Generate CI/CD pipelines, Docker, deploy configs
+# Generate CI/CD pipelines, Docker, and deploy configs
 pygenkit generate
 
 # Check system requirements
 pygenkit doctor
 ```
 
+## Example Output
+
+```text
+Project: my-app
+Version: 0.1.0
+Python: >=3.12
+Build backend: setuptools
+License: MIT
+CI/CD: GitHub Actions detected
+Status: ready for validation
+```
+
 ## Commands
 
 | Command         | Description                                    |
 |-----------------|------------------------------------------------|
 | `new`           | Scaffold a complete Python project with CI/CD  |
-| `init`          | Create `pygenkit.toml` in an existing project |
+| `init`          | Create `pygenkit.toml` in an existing project  |
 | `inspect`       | Analyze project structure, versions, metadata  |
 | `validate`      | Check version consistency, workflows, security |
 | `generate`      | Generate CI/CD, Docker, and deploy files       |
 | `health`        | Assess project health across 7 categories      |
 | `review`        | Review a GitHub PR diff using AI               |
-| `release-check` | Verify release readiness (coming soon)         |
+| `release-check` | Verify release readiness before tagging        |
 | `doctor`        | Check system for required tools                |
 
 ## Usage
@@ -60,7 +95,7 @@ pygenkit init my-project
 # Inspect project
 pygenkit inspect
 
-# Validate
+# Validate project metadata, workflows, and security
 pygenkit validate
 
 # Generate GitHub Actions CI/CD pipelines
@@ -90,9 +125,9 @@ pygenkit generate --force
 Scans your project and reports:
 
 - Project name, version, module
-- Build backend (setuptools, hatchling, poetry, etc.)
+- Build backend: setuptools, hatchling, poetry, etc.
 - Python version requirement
-- License type (MIT, Apache, GPL, etc.)
+- License type: MIT, Apache, GPL, etc.
 - Version consistency between `pyproject.toml`, `__init__.py`, `debian/changelog`, and git tags
 - CI/CD workflow detection
 - Debian packaging status
@@ -101,37 +136,37 @@ Scans your project and reports:
 
 Runs three categories of checks:
 
-- **Version**: consistency across `pyproject.toml`, `__init__.py`, `debian/changelog`, git tags
-- **Workflow**: YAML validity, missing metadata, outdated actions (`checkout@v3`), SHA pin warnings, script injection
-- **Security**: missing permissions blocks, hardcoded secrets, PyPI publish without protected environment
+- **Version**: consistency across `pyproject.toml`, `__init__.py`, `debian/changelog`, and git tags
+- **Workflow**: YAML validity, missing metadata, outdated actions, SHA pin warnings, and script injection risks
+- **Security**: missing permissions blocks, hardcoded secrets, and PyPI publishing without a protected environment
 
 ## Generate
 
-Generates files from Jinja2 templates based on `pygenkit.toml`:
+Generates files from Jinja2 templates based on `pygenkit.toml`.
 
 ### GitHub Actions
 
-| File                   | Description                               |
-|------------------------|-------------------------------------------|
-| `.github/workflows/ci.yml` | Ruff lint, MyPy type-check, Pytest      |
-| `.github/workflows/release.yml` | Build wheel, create GitHub Release |
-| `.github/workflows/publish-pypi.yml` | Trusted PyPI publishing     |
-| `.github/workflows/publish-launchpad.yml` | dput to Launchpad PPA   |
+| File                                      | Description                          |
+|-------------------------------------------|--------------------------------------|
+| `.github/workflows/ci.yml`                | Ruff lint, MyPy type-check, Pytest   |
+| `.github/workflows/release.yml`           | Build wheel and create GitHub Release |
+| `.github/workflows/publish-pypi.yml`      | Trusted PyPI publishing              |
+| `.github/workflows/publish-launchpad.yml` | dput to Launchpad PPA                |
 
 ### Docker
 
-| File                 | Description            |
-|----------------------|------------------------|
-| `Dockerfile`         | Multi-stage build      |
-| `docker-compose.yml` | Service configuration  |
+| File                 | Description           |
+|----------------------|-----------------------|
+| `Dockerfile`         | Multi-stage build     |
+| `docker-compose.yml` | Service configuration |
 
 ### Deploy
 
-| File            | Platform |
-|-----------------|----------|
-| `fly.toml`      | Fly.io   |
-| `Procfile`      | Heroku   |
-| `railway.json`  | Railway  |
+| File           | Platform |
+|----------------|----------|
+| `fly.toml`     | Fly.io   |
+| `Procfile`     | Heroku   |
+| `railway.json` | Railway  |
 
 ## Configuration (`pygenkit.toml`)
 
@@ -197,9 +232,10 @@ pygenkit doctor
 ```
 
 Checks for:
+
 - Python 3.12+
 - Git
-- GitHub CLI (gh)
+- GitHub CLI (`gh`)
 - GPG
 - dput
 - debhelper
@@ -208,13 +244,9 @@ Checks for:
 
 ## Publishing setup
 
-PyPI publishing uses Trusted Publishing (OIDC), so it does not require a long-lived API
-token. Configure the `pypi` environment on GitHub and authorize `release.yml` as a
-Trusted Publisher for the `pygenkit` project on PyPI. Set the repository variable
-`PYPI_ENABLED=true` to enable the publish step.
+PyPI publishing uses Trusted Publishing (OIDC), so it does not require a long-lived API token. Configure the `pypi` environment on GitHub and authorize `release.yml` as a Trusted Publisher for the `pygenkit` project on PyPI. Set the repository variable `PYPI_ENABLED=true` to enable the publish step.
 
-Launchpad publishing requires a PPA and an OpenPGP key registered with the Launchpad
-account. Add these secrets to the `launchpad` GitHub environment:
+Launchpad publishing requires a PPA and an OpenPGP key registered with the Launchpad account. Add these secrets to the `launchpad` GitHub environment:
 
 - `GPG_PRIVATE_KEY`
 - `GPG_PASSPHRASE`
@@ -222,7 +254,7 @@ account. Add these secrets to the `launchpad` GitHub environment:
 
 ## Architecture
 
-```
+```text
 src/pygenkit/
 ├── cli/              # CLI commands (Typer)
 │   └── commands/     # init, inspect, validate, generate, release-check, doctor
@@ -258,7 +290,7 @@ src/pygenkit/
 
 PyGenKit itself follows the professional workflow it generates for other projects.
 
-```
+```text
 feature branch → Pull Request → CI checks → merge to main → tag → release
 ```
 
@@ -288,33 +320,33 @@ git push origin v0.x.x     # triggers Release workflow
 
 ### Branch naming
 
-| Prefix     | Purpose                |
-|------------|------------------------|
-| `feat/*`   | New features           |
-| `fix/*`    | Bug fixes              |
-| `refactor/*` | Code improvements    |
-| `docs/*`   | Documentation          |
-| `ci/*`     | CI/CD changes          |
+| Prefix       | Purpose            |
+|--------------|--------------------|
+| `feat/*`     | New features       |
+| `fix/*`      | Bug fixes          |
+| `refactor/*` | Code improvements  |
+| `docs/*`     | Documentation      |
+| `ci/*`       | CI/CD changes      |
 
 ## Branch Protection
 
-The `main` branch **must be protected** in the GitHub repository settings:
+The `main` branch should be protected in the GitHub repository settings.
 
 ### Required settings
 
-| Setting                          | Solo | Team |
-|----------------------------------|------|------|
-| Require pull request before merging | Yes | Yes |
-| Require status checks to pass (CI)  | Yes | Yes |
-| Block force pushes                   | Yes | Yes |
-| Restrict deletions                   | Yes | Yes |
+| Setting                             | Solo | Team |
+|-------------------------------------|------|------|
+| Require pull request before merging | Yes  | Yes  |
+| Require status checks to pass       | Yes  | Yes  |
+| Block force pushes                  | Yes  | Yes  |
+| Restrict deletions                  | Yes  | Yes  |
 | Required approvals                  | 0    | 1    |
 
 When working alone, skip approval requirements. When adding maintainers, set **Required approvals: 1**.
 
 ### How to configure
 
-```
+```text
 GitHub repo → Settings → Branches → Add branch protection rule
   Branch name pattern: main
   ☑ Require a pull request before merging
@@ -324,6 +356,15 @@ GitHub repo → Settings → Branches → Add branch protection rule
   ☑ Restrict deletions
 ```
 
+## Roadmap
+
+- Add richer CLI examples and screenshots
+- Add code coverage reporting
+- Add project templates for FastAPI, CLI tools, and libraries
+- Add semantic versioning helpers
+- Add optional plugin support for custom generators
+- Expand release checks for PyPI, Debian, and Launchpad workflows
+
 ## Requirements
 
 - Python 3.12+

{pygenkit-0.2.0 → pygenkit-0.2.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pygenkit"
-version = "0.2.0"
+version = "0.2.4"
 description = "Professional Python project generator — PyPI, APT, and Launchpad ready"
 readme = "README.md"
 requires-python = ">=3.12"

{pygenkit-0.2.0 → pygenkit-0.2.4}/src/pygenkit/__init__.py

@@ -1,2 +1,2 @@
 __all__ = ["__version__"]
-__version__ = "0.2.0"
+__version__ = "0.2.4"

{pygenkit-0.2.0 → pygenkit-0.2.4}/src/pygenkit/health/checks.py

@@ -131,7 +131,7 @@ def check_cicd(root: Path) -> CategoryScore:
 
     wf_dir = root / ".github" / "workflows"
     if wf_dir.is_dir():
-        wf_files = list(wf_dir.glob("*.yml"))
+        wf_files = detect_inspector.workflow_files(root)
         score.details.append(f"{len(wf_files)} workflow file(s)")
         if wf_files:
             score.passed += 1
@@ -139,7 +139,7 @@ def check_cicd(root: Path) -> CategoryScore:
 
         has_ci = any("ci" in f.name.lower() for f in wf_files)
         has_release = any("release" in f.name.lower() for f in wf_files)
-        has_pypi = any("pypi" in f.name.lower() for f in wf_files)
+        has_pypi = detect_inspector.has_pypi_publish_workflow(root)
 
         if has_ci:
             score.passed += 1
@@ -210,7 +210,7 @@ def check_security(root: Path) -> CategoryScore:
     wf_dir = root / ".github" / "workflows"
     has_permissions = False
     if wf_dir.is_dir():
-        for f in wf_dir.glob("*.yml"):
+        for f in detect_inspector.workflow_files(root):
             content = f.read_text(encoding="utf-8", errors="replace")
             if "permissions:" in content:
                 has_permissions = True

{pygenkit-0.2.0 → pygenkit-0.2.4}/src/pygenkit/inspector/api.py

@@ -83,16 +83,16 @@ def _inspect_workflows(root: Path) -> WorkflowInspection:
     if not wf_dir.is_dir():
         return wf
 
-    for f in wf_dir.glob("*.yml"):
+    for f in detect_inspector.workflow_files(root):
         wf.files.append(f.name)
         content = f.read_text(encoding="utf-8", errors="replace")
-        if "pypi" in content.lower() or "publish" in content.lower():
-            wf.has_pypi_publish = True
         if "launchpad" in content.lower() or "ppa" in content.lower():
             wf.has_launchpad = True
         if "test" in content.lower() or "lint" in content.lower():
             wf.has_ci = True
 
+    wf.has_pypi_publish = detect_inspector.has_pypi_publish_workflow(root)
+
     return wf