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@c4afcb095a6cb2fe41e95727bfa75120b843f8fb # v6.23.3
Metadata
Release files for repo-standards 6.23.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repo_standards-6.23.3.tar.gz | 152.4 kB | With provenance | Details for repo_standards-6.23.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repo_standards-6.23.3-py3-none-any.whl | Python 3 | none | any | Details for repo_standards-6.23.3-py3-none-any.whl |
Total release size: 329.0 kB
Release files / repo_standards-6.23.3.tar.gz
| Download URL | repo_standards-6.23.3.tar.gz |
|---|---|
| Size | 152.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
377ae578866f56d4ab2665df0457d336173dc1f4752369dc99f93f4366ea8418
|
|
BLAKE2b-256 checksum How to use checksums |
9aafa139d4db0e00656ae1c2c22b4d084487e7bd38f1a6f41d60e18e694d6497
|
| 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 12, 2026.
Transparency logRelease files / repo_standards-6.23.3-py3-none-any.whl
| Download URL | repo_standards-6.23.3-py3-none-any.whl |
|---|---|
| Size | 176.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
80cec2581f6a71387df41c55f528717ff63f69c0ae3a323dc3ef8a86beda790b
|
|
BLAKE2b-256 checksum How to use checksums |
f43a661f469589aa0335da7318a95f4377531c72c54ba7d1b631ea4b2b71bb83
|
| 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 12, 2026.
Transparency logSecurity for repo-standards 6.23.3
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.
Attestation for repo_standards-6.23.3.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 12, 2026.
Transparency logA 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.