Skarmory
Fast Python code analysis, powered by Rust.
Skarmory is building a native Rust analysis engine with a Python API and a native command-line interface. The initial compatibility target is Skylos 5.7.0's Python analysis behavior: useful findings, framework awareness, explainable confidence, and explicit analysis limits.
Status
Skarmory has a native Phase 0 prototype for a flat, closed-world Python 3.11 application. The CLI and Python SDK report unreachable functions with evidence and explicit coverage. See the prototype contract for the supported source subset and the benchmark report for comparisons with the pinned Skylos reference.
Plans
| Document | Contents |
|---|---|
| Architecture | Shared Rust engine, Python semantics, project graph, caching, evidence, and integration boundaries |
| Roadmap | Phases, dependencies, acceptance gates, and initial engineering tasks |
| Compatibility | Pinned Skylos target, promised surfaces, exclusions, and discrepancy policy |
| Architecture decision | Why the CLI and Python SDK share a native engine |
| Conformance strategy | Differential compatibility and independently reviewed correctness cases |
| Benchmark strategy | Matched workloads, cache states, accuracy gates, and unmeasured performance goals |
The next milestone expands the prototype into the Python dead-code preview.
Repository layout
| Path | Role |
|---|---|
crates/analysis_core |
skarmory_core: shared native engine boundary |
crates/python_frontend |
skarmory_python: Ruff parser adapter and prototype fact extraction |
crates/cli |
skarmory_cli: native skarmory executable |
crates/python_bindings |
skarmory_bindings: PyO3 extension installed as skarmory._native |
python/skarmory |
Python API, typing information, and development version |
tests/python |
Source and installed-wheel tests |
tests/conformance |
Reviewed fixtures and pinned reference metadata |
benchmarks |
Measurement harness, results, and evaluation plan |
docs |
Design documents and delivery roadmap |
Development
Use Python 3.11 or newer and a Rust toolchain with rustfmt and clippy.
The workspace requires Rust 1.96 or later for the pinned Ruff crates. CI tests
the minimum, and the local toolchain file selects stable Rust.
Native CLI
cargo run --locked -p skarmory_cli -- --help
cargo run --locked -p skarmory_cli -- tests/conformance/fixtures/reachable
The CLI emits one JSON report per scan. A complete report exits 0. Incomplete coverage is explicit and exits 2.
Python SDK
In a virtual environment, build and install the local package:
python -m pip install .
python -c "import skarmory; print(skarmory.analyze('tests/conformance/fixtures/reachable'))"
Maturin builds the native extension from source. The SDK returns a report
dictionary with a coverage.status field. Install the native CLI separately with
cargo install --locked --path crates/cli. The combined-wheel layout is an
experiment documented in the Phase 0 evidence.
Checks
python scripts/check_structure.py
cargo fmt --all -- --check
cargo clippy --locked --workspace --all-targets -- -D warnings
cargo test --locked --workspace
cargo build --locked -p skarmory_cli
python tests/conformance/check_phase0.py target/debug/skarmory
python -m unittest discover -s tests/python -v
The Python test command uses the installed SDK. Run the source-only failure check on POSIX with:
PYTHONPATH=python python -m unittest discover -s tests/python -v
CI sets SKARMORY_REQUIRE_NATIVE=1 for installed-wheel tests, so a missing
extension cannot be hidden by the source-only test mode. The packaging matrix covers Linux, macOS, and Windows and includes a source
distribution rebuild.
Compatibility and performance
The reference is Skylos 5.7.0,
commit 87978e69adf91b3811e97b00c40aa39d7937cd94. The machine-readable baseline is
in tests/conformance/baselines/skylos-5.7.0.toml.
Ruff is an architectural and responsiveness reference. Whole-project reachability and security analysis have different workloads from local linting; all speed targets in this repository are provisional and unmeasured. A faster run with missing rules, fewer analyzed files, or incomplete coverage is not a matched performance result.
Skarmory is an independent project distributed under the MIT license. See CONTRIBUTING.md for the development workflow and rules for preserving compatibility evidence.
Metadata
Release files for skarmory 0.0.1
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 |
|---|---|---|---|---|
| skarmory-0.0.1.tar.gz | 45.9 kB | Without provenance | Details for skarmory-0.0.1.tar.gz |
Built distributions (wheels)
Total release size: 8.1 MB
Release files / skarmory-0.0.1.tar.gz
| Download URL | skarmory-0.0.1.tar.gz |
|---|---|
| Size | 45.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e6e493948d747293e1e95eda276bc5b51d64b078acb10f9ebc5bb634608c631
|
|
BLAKE2b-256 checksum How to use checksums |
7c043f339cb97c145abbe49a1d730fee3ac0ebf63d3b043feea72d454b12d9e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-win_arm64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-win_arm64.whl |
|---|---|
| Size | 940.6 kB |
| Tags | CPython 3.11 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
5319ab9bac96891d2f2dbd42b957776127f7564fff1ef90a182ce7313e278f0d
|
|
BLAKE2b-256 checksum How to use checksums |
689235c8dd14ab49f97dd2114a6e06a4f15cfcdb18ac0bad00962811534ecb0f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-win_amd64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 963.3 kB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
a0b13e643d5bc6054940e6caf82dc4b5b7d83a18fb1f3428c4206d99e6570c16
|
|
BLAKE2b-256 checksum How to use checksums |
482faa5c7f07bde5eca2c697c5268e916d70ac3c5e44a42a51631c780a5efc2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-musllinux_1_2_x86_64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7cf7e8996a6151e0ba87a9aac98db7427409f99aeb828a7913d2a4f786c40e7b
|
|
BLAKE2b-256 checksum How to use checksums |
f06e4dd9617cc81c2f3a7ef899ad4bdef8b90a07813b01abfeb93d29202ee994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-musllinux_1_2_aarch64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
41e601fd029489616648c4d311c1ace8e8c42707bd923f2c38ce5a1ae69fa9c5
|
|
BLAKE2b-256 checksum How to use checksums |
aa2c253a7160fc419eeab07826dac7eabc5952efa8e9f1d563f7571b0b375714
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-manylinux_2_28_aarch64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
a1d1bf59d6910f2f09a6b3763a119b9530360ca240cf5268a36d1d9d85c65913
|
|
BLAKE2b-256 checksum How to use checksums |
5191220e7a1ea54bf302774bf3078edd19fd8c2019c0d902983c87132c591d5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f3b498b8b87d820eb5554b6c7eae052869030b7fbc5d300d923eec16f4825ff4
|
|
BLAKE2b-256 checksum How to use checksums |
6a64491c8c417b000cf3d600c1d94c35ba82919ea72e717ad6adf673f2aec752
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f7672a2960a470ab0d3746a1f2d48570ba977824dc227e41444ff9be505d7221
|
|
BLAKE2b-256 checksum How to use checksums |
534d11f24783dd2cceeebf0e3b9c068b840ad5b878dafceeb127a307919892b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Release files / skarmory-0.0.1-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | skarmory-0.0.1-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 1.0 MB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
660702d164a4d62a6e53ab46be85ec65d2a555b41a61efba222de1e2a36c2b76
|
|
BLAKE2b-256 checksum How to use checksums |
fed2b07240657cabbd9f647881cab4ba620ce765fd1b31e69ecd8e2c8c171c0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.18
|
Security for skarmory 0.0.1
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.