code-standards

One deterministic quality gate for Sarj Python, TypeScript, Swift, Kotlin, shell, SQL, IaC, and repository policy.

uv tool install --python 3.14 code-standards

Adopt the repository once with code-standards setup. It installs one canonical staged gate that includes semantic lint and repository policy, plus commit-message and pull-request history enforcement. Do not install Repo Standards separately.

code-standards setup
code-standards check
code-standards check --rule python:no-excessive-cognitive-complexity src/
code-standards fix
code-standards doctor
code-standards update

Use repeatable check --rule ENGINE:ID selectors to select native rules, ESLint rules, or managed security audits. Exclusions, baselines, and severities still apply; Ruff selectors are not supported. Native linters and ESLint execute only selected rules. ESLint retains configured parsers, options, severities, and suppression directives.

Terraform, Kubernetes, and GitHub Actions adoption adds isolated Checkov 3.3.20 and zizmor 1.30.1 runtimes. Setup and generated CI prewarm these tools; checks run offline with packaged policy. Use --rule checkov:CKV_GCP_95 or --rule zizmor:template-injection to select upstream audits. Their findings start as warnings, use the canonical diagnostic baseline, and retain upstream IDs. Checkov honors its inline suppression directives; zizmor ignore comments are disabled. Explicit zizmor selectors include auditor-persona checks; online-only audits cannot run offline. Parsing or execution failures leave the analysis incomplete. Image digest evidence for source templates is deferred to their rendered deployment artifacts.

check --jobs 2 overlaps native analysis with the external-tool pipeline. The default is --jobs 1; external tools remain sequential and report ordering is deterministic.

Documentation · Source

Metadata

Release files for code-standards 8.33.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 code-standards 8.33.1
File	Size	Uploaded
code_standards-8.33.1.tar.gz	649.3 kB	Oct 7, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for code-standards 8.33.1
File	Interpreter	ABI	Platform	Reset
code_standards-8.33.1-py3-none-any.whl 716.2 kB Oct 7, 2026	Python 3	none	any	Details

Total release size: 1.4 MB

Release files / code_standards-8.33.1.tar.gz

Download URL	code_standards-8.33.1.tar.gz
Size	649.3 kB
Tags	Source
SHA-256 checksum How to use checksums	`93d48efa723792094466e29701451b7175b80a5769f6d31963450b5782de29e6`
BLAKE2b-256 checksum How to use checksums	`f77993d89508efb7b6d13312d5beef61dc6af5d4312cf202489bcf27ec65603e`
Upload date	Oct 7, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/sarj-ai/code-standards
Publishing commit: github.com/sarj-ai/code-standards/tree/18fe57305ed339477a70551c8c67548245d9fffa

Workflow

Publishing configuration: github.com/sarj-ai/code-standards/blob/18fe57305ed339477a70551c8c67548245d9fffa/.github/workflows/release.yml
Publishing logs: github.com/sarj-ai/code-standards/actions/runs/37642501335/attempts/1

Artifact

Subject: code_standards-8.33.1.tar.gz
SHA-256 checksum: 93d48efa723792094466e29701451b7175b80a5769f6d31963450b5782de29e6 Verifying attestations

Release files / code_standards-8.33.1-py3-none-any.whl

Download URL	code_standards-8.33.1-py3-none-any.whl
Size	716.2 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`6f169157759c1ee29f88a7bf113c4c01a50e1b228e40b1d30834e5fbb6d3a824`
BLAKE2b-256 checksum How to use checksums	`4a6af6542e8d39e8b153f9aee53c8342458f7a792d8a724f7ad45c4c71f5f00e`
Upload date	Oct 7, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/sarj-ai/code-standards
Publishing commit: github.com/sarj-ai/code-standards/tree/18fe57305ed339477a70551c8c67548245d9fffa

Workflow

Publishing configuration: github.com/sarj-ai/code-standards/blob/18fe57305ed339477a70551c8c67548245d9fffa/.github/workflows/release.yml
Publishing logs: github.com/sarj-ai/code-standards/actions/runs/37642501335/attempts/1

Artifact

Subject: code_standards-8.33.1-py3-none-any.whl
SHA-256 checksum: 6f169157759c1ee29f88a7bf113c4c01a50e1b228e40b1d30834e5fbb6d3a824 Verifying attestations