scm-kit
Polyglot formatting and linting toolkit. Provides two commands — scm-format
and scm-lint — that auto-detect which tools to run based on the files in your
repo.
Prerequisites
Usage
# Install and run via uvx:
uvx --from scm-kit scm-format
uvx --from scm-kit scm-lint
uvx --from scm-kit scm-lint -a # lint all files, not just changed
# Or add to your Makefile:
# fmt:
# @uvx --from scm-kit scm-format
# lint:
# @uvx --from scm-kit scm-lint
What runs
| Language/Files | Format | Lint |
|---|---|---|
Go (go.mod) |
gofmt |
go vet |
JS/TS/CSS/JSON (biome.json) |
Biome | Biome |
| HTML, Markdown, YAML | Prettier | Prettier |
Python (.py) |
Ruff (fix + format) | Ruff (check + format check), Pyright |
TypeScript (tsconfig.json) |
— | tsc --noEmit |
Tools are invoked via npx or uvx, so they don't need to be pre-installed.
Go tools are optional — skipped if not on PATH.
Each tool is skipped when no matching files or config is present, so a Python-only repo won't invoke Biome or Prettier.
Config files
Projects using scm-kit should include their own config files as needed:
.ruff.toml— Ruff linter config (Python)biome.json— Biome formatter/linter config (JS/TS/CSS/JSON)pyrightconfig.json— Pyright type-checker config (Python)
Lint flags
- Default: Pyright checks only changed files (vs
HEAD+ untracked), since it is slow on large codebases. All other linters check the full tree. -a/--all-files: Pyright checks all files.
Development
To test local changes before publishing, use the dev- Makefile targets. These
run against the local source instead of the published package:
make dev-fmt # format using local scm-kit
make dev-lint # lint using local scm-kit
make dev-lint-all # lint all files using local scm-kit
Publishing
rm -rf dist
uv build
UV_PUBLISH_TOKEN=pypi-xxxxx uv publish
Generate a token at https://pypi.org/manage/account/token/.
1 maintainer
Metadata
1 maintainer
Release files for scm-kit 0.0.14
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 | |
|---|---|---|---|---|
| scm_kit-0.0.14.tar.gz | 4.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scm_kit-0.0.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 9.7 kB
Release files / scm_kit-0.0.14.tar.gz
| Download URL | scm_kit-0.0.14.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ea138107815f4b9f94efd10416be3466174010271384a9ab7c6060683d06319
|
|
BLAKE2b-256 checksum How to use checksums |
b7174df05745fe155c575b1747e35605a1453bb57a09eed31884daa3c8ceb387
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / scm_kit-0.0.14-py3-none-any.whl
| Download URL | scm_kit-0.0.14-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d34093f7b52a0c6cb57a4ec5549da2cb6d3856bab6d75e897d14026ef7c3e282
|
|
BLAKE2b-256 checksum How to use checksums |
d39671640d4753ec8edc306ceb967acebb5bde66a2bbaac854b968b4faceb353
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.2 {"installer":{"name":"uv","version":"0.10.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for scm-kit 0.0.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
