Skip to main content

Maintainer Ready

Maintainer Ready is a small command-line tool that audits whether an open-source repository has the public signals maintainers usually need before a project can grow: a useful README, a license, contribution guidance, security policy, issue templates, pull request template, tests, CI, changelog, and release evidence.

It is built for solo maintainers and small teams who want a practical checklist, not a heavy governance framework.

Why this exists

Many promising open-source projects fail to look trustworthy because the basics are scattered or missing. Maintainer Ready gives maintainers a repeatable report they can run before a release, before asking for contributors, or before sharing the project publicly.

Install

python -m pip install maintainer-ready

For local development:

python -m pip install -e .

Usage

Audit the current repository:

maintainer-ready .

Write machine-readable output:

maintainer-ready . --json

Fail when the score is below a threshold:

maintainer-ready . --min-score 80

Example Output

Maintainer Ready report for .
Score: 86/100

PASS  README                 README.md has substantial project context
PASS  License                LICENSE found
PASS  Contribution guide     CONTRIBUTING.md found
WARN  Security policy        SECURITY.md is missing
PASS  Issue templates        GitHub issue templates found
PASS  Pull request template  Pull request template found
PASS  Tests                  Test directory found
PASS  CI                     GitHub Actions workflow found
PASS  Changelog              CHANGELOG.md found
WARN  Release evidence       No local git tag or release note heading found

What It Checks

Maintainer Ready looks for public, verifiable signals:

  • project purpose and usage documentation
  • open-source license
  • contribution process
  • security reporting path
  • issue and pull request templates
  • tests and CI
  • changelog or release notes
  • local release evidence such as git tags or version headings

These checks are intentionally simple. They are meant to make a repository easier for humans to trust and contribute to.

Roadmap

  • GitHub API mode for stars, forks, open issues, merged pull requests, and release activity
  • optional PyPI and npm download checks
  • Markdown report output for posting in issues
  • repository badge generation
  • sample GitHub Action that comments readiness reports on pull requests

Contributing

Contributions are welcome. Please read CONTRIBUTING.md before opening an issue or pull request.

License

MIT

Metadata

Release files for maintainer-ready 0.1.0

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-ready 0.1.0
File Size Uploaded
maintainer_ready-0.1.0.tar.gz 11.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for maintainer-ready 0.1.0
File Interpreter ABI Platform
maintainer_ready-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 18.3 kB

Release files / maintainer_ready-0.1.0.tar.gz

Download URL maintainer_ready-0.1.0.tar.gz
Size 11.4 kB
Tags Source
SHA-256 checksum
How to use checksums
3923f987b34a150ddeb632c2899825b93f3a4d044b7dc7bebb9673e0d80dbbb0
BLAKE2b-256 checksum
How to use checksums
85fabe77d62b595a2e241629527c9bc04df9fe10322a18cb79ca406618842264
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 12, 2026.

Transparency log

Release files / maintainer_ready-0.1.0-py3-none-any.whl

Download URL maintainer_ready-0.1.0-py3-none-any.whl
Size 6.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7389e7d428ecba7c7dbb7b6dda63d0b18486a134561213c80436f698fa89ff30
BLAKE2b-256 checksum
How to use checksums
11babe6773056204bd19130e1446c9e199f914aa42bc3bfccfcec99c594e8a17
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 12, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

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