Skip to main content

Awesome Maintainer Defense

English · Tiếng Việt · 日本語

Awesome Maintainer Defense is an offline, read-only repository auditor and a set of reversible maintainer controls. It inspects local governance files and GitHub Actions trust boundaries without a token or network request. It does not execute repository code, inspect live GitHub settings, or identify who wrote a contribution.

Quickstart

Python 3.10 or newer is required.

make standalone
python3 dist/maintainer-defense-kit.py audit .

The audit prints evidence, severity, and a stable rule ID. A finding is a review lead, not proof that a repository is compromised or a contributor is malicious.

What the auditor checks

  • Missing security, ownership, structured-intake, dependency-update, and branch-policy evidence.
  • Excessive workflow token authority, mutable Action references, privileged execution of pull-request input, shell interpolation, and unsafe cross-workflow artifacts.
  • Destructive moderation, identity/history proxies, and missing appeal paths.

The rule registry and review requirements are in Auditor rules.

From finding to reviewed patch

fix generates a unified diff and never edits the target repository:

python3 dist/maintainer-defense-kit.py fix . --output recommended.patch
git apply --check recommended.patch

Review the evidence and patch in repository context. Apply it only through the repository's normal ownership and CI process.

The audit-to-action diagram shows the complete governance path: scope the authorized target, inspect it offline, assess evidence, propose a patch, obtain an owner decision, then apply and record the change through the normal repository workflow.

Evidence boundaries

Tested contracts cover deterministic detection, JSON/SARIF output, patch-only remediation, installer conflict handling, and shipped workflow invariants. The project does not claim field accuracy across representative repositories, live GitHub-settings coverage, compliance, or proof of authorship or intent. See Kit assurance and Threat model.

Install options

PyPI with an isolated application environment:

pipx install maintainer-defense-kit==1.1.1
maintainer-defense audit .

Verified standalone on POSIX systems:

curl -fLO https://github.com/thangldw/awesome-maintainer-defense/releases/download/v1.1.1/maintainer-defense-kit.py
curl -fLO https://github.com/thangldw/awesome-maintainer-defense/releases/download/v1.1.1/maintainer-defense-kit.py.sha256
shasum -a 256 -c maintainer-defense-kit.py.sha256
python3 maintainer-defense-kit.py audit .

Verified standalone on PowerShell:

Invoke-WebRequest https://github.com/thangldw/awesome-maintainer-defense/releases/download/v1.1.1/maintainer-defense-kit.py -OutFile maintainer-defense-kit.py
Invoke-WebRequest https://github.com/thangldw/awesome-maintainer-defense/releases/download/v1.1.1/maintainer-defense-kit.py.sha256 -OutFile maintainer-defense-kit.py.sha256
$Expected = ((Get-Content maintainer-defense-kit.py.sha256 -Raw).Trim() -split '\s+')[0].ToLowerInvariant()
$Actual = (Get-FileHash maintainer-defense-kit.py -Algorithm SHA256).Hash.ToLowerInvariant()
if ($Actual -ne $Expected) { Write-Error "SHA-256 mismatch"; exit 1 }
python maintainer-defense-kit.py audit .

Release channels and recovery rules are documented in Distribution.

Documentation

Curated catalog

The catalog is a secondary, evidence-reviewed index of maintainer-defense resources. Inclusion is not an endorsement. Review permissions, data boundaries, maximum effects, maintenance state, and licensing before adoption. See the generated catalog.

Contributing and support

Read Contributing before proposing a rule, product change, translation, or catalog entry. Use Support for public requests and Security for private vulnerability reporting.

License

Released under the MIT License.

Metadata

Release files for maintainer-defense-kit 1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for maintainer-defense-kit 1.1.1
File Size Uploaded Provenance Actions
maintainer_defense_kit-1.1.1.tar.gz 124.4 kB With provenance Details for maintainer_defense_kit-1.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for maintainer-defense-kit 1.1.1
File Interpreter ABI Platform Actions
maintainer_defense_kit-1.1.1-py3-none-any.whl Python 3 none any Details for maintainer_defense_kit-1.1.1-py3-none-any.whl

Total release size: 167.7 kB

Release files / maintainer_defense_kit-1.1.1.tar.gz

Download URL maintainer_defense_kit-1.1.1.tar.gz
Size 124.4 kB
Tags Source
SHA-256 checksum
How to use checksums
ccab463b15a78b3dfbe37a3f9002b5524aaa5d67afe61bf6ff2a5b05f86fa902
BLAKE2b-256 checksum
How to use checksums
4897120623842fed96bf87bafe8adceab658fe780de115166b61cb39f8fe385e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.

Transparency log

Release files / maintainer_defense_kit-1.1.1-py3-none-any.whl

Download URL maintainer_defense_kit-1.1.1-py3-none-any.whl
Size 43.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f112c3ce3e11efcaf4c150a3f26c72fc1e041ec92276a9d625ba6e818433b2ea
BLAKE2b-256 checksum
How to use checksums
5e1003380c52dd838c2f934085e4e23adb2f7c164bec2fa9a5a52f7eda0ce3ee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.

Transparency log

Security for maintainer-defense-kit 1.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for maintainer_defense_kit-1.1.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 23, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page