Skip to main content

repo-standards

repo-standards measures pull-request review size without executing repository code. Its repository rules are available for review but remain disabled until individually approved and explicitly activated by a consumer.

Where rules belong

  • Exact tracked-tree facts—filenames, placement, topology, migrations, pull-request size, ownership, delivery/GitHub state, and repository-wide API/document sets—belong here.
  • Source and configuration semantics for Python, TypeScript, SQL, Terraform/HCL, Markdown, YAML, JSON, and shell belong in sarj-ai/code-standards.

Run it

Sarj repositories should use the single Code Standards setup path. It installs the canonical staged repository check, managed commit-message check, and authoritative pull-request history workflow without creating a second Python environment:

uvx --no-config --isolated --python 3.14 --from code-standards code-standards setup
code-standards doctor

Use the current release without installing it:

uvx --from repo-standards repo-standards pull-request size . --base origin/main

For a persistent user installation:

uv tool install repo-standards
repo-standards pull-request size . --base origin/main

Upgrade with uv tool upgrade repo-standards. Automation should pin the package version or the GitHub Action's full commit SHA.

Safety model

  • Repository contents come from one exact Git tree.
  • Workflow YAML and API descriptions are parsed as inert data.
  • Missing required evidence produces an inconclusive result rather than a false pass.
  • Advisory commit-history analysis reports incomplete evidence without blocking local commits.
  • The linter has no autofix or repository mutation mode.

Development

uv sync --locked
uv run pytest
uv run ruff check .
uv run basedpyright

Build the same wheel and source distribution used by publishing:

uv build --no-sources

Releases are reconcilable. The protected workflow independently repairs a missing PyPI publication or GitHub Release from the same verified source revision.

GitHub Action

- uses: sarj-ai/repo-standards@e67c6281916c655a9aec32ae528eea368d74ecc3 # v6.23.0

Metadata

Release files for repo-standards 6.23.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 repo-standards 6.23.0
File Size Uploaded Provenance Actions
repo_standards-6.23.0.tar.gz 151.7 kB With provenance Details for repo_standards-6.23.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for repo-standards 6.23.0
File Interpreter ABI Platform Actions
repo_standards-6.23.0-py3-none-any.whl Python 3 none any Details for repo_standards-6.23.0-py3-none-any.whl

Total release size: 327.7 kB

Release files / repo_standards-6.23.0.tar.gz

Download URL repo_standards-6.23.0.tar.gz
Size 151.7 kB
Tags Source
SHA-256 checksum
How to use checksums
b727070471c6a6d903b6d86f4c60805445babf7a46a849e467f3a8de8fc48a84
BLAKE2b-256 checksum
How to use checksums
5743d99b242ee911aaa30ef98bb113e1c77c8dda7a6700488c3366bd47c18400
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 11, 2026.

Transparency log

Release files / repo_standards-6.23.0-py3-none-any.whl

Download URL repo_standards-6.23.0-py3-none-any.whl
Size 176.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ed995f9040eff300bf9b52b6324cb111fb8b5e43382a3b2390d99ed27a6e9877
BLAKE2b-256 checksum
How to use checksums
e43805ea62d28849a9cb9da3b5ceb462ad983f3494646701397971af5b56d5d3
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 11, 2026.

Transparency log

Security for repo-standards 6.23.0

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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for repo_standards-6.23.0.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 Nov 11, 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

6.23.0 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