repomatic implements most of the practices described in Astral's Open Source Security at Astral post, baked into a drop-in setup that any maintainer can inherit by pointing their workflows at the reusable callers.

Every third-party GitHub Action executes with access to GITHUB_TOKEN and repository secrets. Each action is a trust delegation: you depend on the maintainer's security practices, their CI pipeline, and their transitive dependencies. A compromised action can steal secrets, inject code into builds, or tamper with releases.

repomatic has systematically eliminated 18 third-party actions since late 2025, replacing them with internal CLI commands, SHA-256-verified binary downloads, and runner built-in tools:

The remaining third-party actions (5 of 14 total) are:

Replacement strategies, ordered from most to least isolated:

1. Internal CLI: the operation runs inside repomatic Python code with no external process.
2. Direct binary download: checksummed binary fetched from a GitHub release URL, no action code path involved.
3. Runner built-in: uses tools pre-installed on the GitHub Actions runner (gh, Rust toolchain).
4. First-party replacement: swaps a community action for an official actions/* equivalent maintained by GitHub.

Eight separate Python linters and formatters have been absorbed into ruff, eliminating eight runtime or dev dependencies:

The mdformat-black plugin was also swapped for mdformat-ruff (Aug 2024): same dependency count, but aligns the Markdown pipeline with ruff's formatting rules.

autopep8 is the only legacy formatter still in use: it handles long-line comment wrapping that ruff does not yet cover.

Five separate packaging and install tools have been absorbed into uv, which now handles dependency management, builds, publishing, auditing, and Python version installation:

uv also consolidated command-line usage that previously required separate tools: pip install became uv pip install / uv sync, pipx became uvx, and actions/setup-python was replaced by astral-sh/setup-uv (counted in the action minimization table above).

Two other Python packages were eliminated outside the ruff/uv consolidations: pipdeptree (replaced by an internal deps-graph implementation) and gitignore-parser (replaced by py-walk).

Several workflows need a REPOMATIC_PAT secret to create PRs that modify files in .github/workflows/ and to trigger downstream workflows. Without it, those jobs silently fall back to the default GITHUB_TOKEN, which lacks the required permissions.

After your first push, the setup-guide job automatically opens an issue with step-by-step instructions to create and configure the token.

All workflows use a concurrency directive to prevent redundant runs and save CI resources. When a new commit is pushed, any in-progress workflow runs for the same branch or PR are automatically cancelled.

Workflows are grouped by:

• Pull requests: {workflow-name}-{pr-number} — Multiple commits to the same PR cancel previous runs
• Branch pushes: {workflow-name}-{branch-ref} — Multiple pushes to the same branch cancel previous runs

release.yaml uses a stronger protection: release commits get a unique concurrency group based on the commit SHA, so they can never be cancelled. This ensures tagging, PyPI publishing, and GitHub release creation complete successfully.

Additionally, cancel-runs.yaml actively cancels in-progress and queued runs when a PR is closed. This complements passive concurrency groups, which only trigger cancellation when a new run enters the same group — closing a PR doesn't produce such an event.

Compiled Python binaries (built with Nuitka --onefile) are frequently flagged as malicious by heuristic AV engines. The onefile packaging technique (self-extracting archive with embedded Python runtime) triggers generic "packed/suspicious" signatures. This is a known issue across the Nuitka ecosystem.

The scan-virustotal job in release.yaml uploads all compiled binaries to VirusTotal on every release. This seeds AV vendor databases to reduce false positive rates for downstream distributors (Chocolatey, Scoop, etc.).

When a release is flagged, the /av-false-positive skill generates per-vendor submission files with pre-written text and form field mappings. The vendor details below document the process for manual reference.

Submit in this order to maximize impact:

1. Microsoft: most influential engine. ML detections (Sabsik, Wacatac) have the broadest downstream effect.
2. BitDefender: powers ~6 downstream vendor engines. Highest detection-removal-per-submission ratio.
3. ESET: email-based channel with no portal dependency. The most reliable submission path.
4. Symantec: ML detections (ML.Attribute.*) may take longer to process.
5. Avast/AVG: shared engine, so one submission covers both.
6. Sophos: PUA detections require justification of the software's legitimate purpose.

Every false-positive submission should include:

• The binary's VirusTotal report link.
• VirusTotal links for the clean .whl and .tar.gz source distributions (as comparison evidence).
• The GitHub release link and direct download URL for the binary.
• Project homepage and PyPI URL.
• License from pyproject.toml.
• Reference to any prior false-positive issue in the repository.

All submission text should mention that the binary is compiled with Nuitka --onefile from an open-source project.

• Microsoft: CORS errors or stuck progress modals during upload (auth session expiring). Workaround: sign out, clear cookies for microsoft.com, sign back in, submit immediately.
• BitDefender: form sometimes returns "Your request could not be registered!" with no details. Retry later.
• Avast: form sometimes returns "An internal error occurred while sending the form." Retry later.