scrybe-cli
Headless CLI binary for Scrybe: render, lint, mermaid encode/decode, and GUI
launcher. Distributed as a maturin binary wheel (scrybe-cli). Python on
the outside, Rust on the inside.
What it does
Provides a scrybe command-line tool with four primary subcommands plus a
bare invocation shortcut. The binary is self-contained — no Python runtime
required at execution time when installed from the wheel.
Role in the architecture
scrybe-cli is the human-facing entry point for headless use and scripting.
It delegates to scrybe-core, scrybe-render, and scrybe-mermaid. It is
also the launcher for the Tauri GUI app: scrybe file.md locates the
Scrybe.app bundle (macOS) or scrybe-app binary and opens the file in it.
Subcommands
| Command | Description |
|---|---|
scrybe render [FILE] |
Render Markdown to HTML (stdin → stdout by default); --theme, --full-html, --output |
scrybe lint FILE |
Word count, headings, code blocks, broken links; --json for machine output; exits 1 if broken links found |
scrybe mermaid embed PNG SOURCE |
Embed Mermaid source into PNG iTXt chunk |
scrybe mermaid extract PNG |
Print embedded Mermaid source, verifying its SHA-256 by default; exit 2 if tampered, --unverified to skip the check (forensics) |
scrybe mermaid verify PNG |
Verify SHA-256 integrity of embedded source; exits 1 if tampered or digest missing |
scrybe open [PATH] |
Launch the Scrybe GUI, optionally at a file or directory |
scrybe version |
Print version and active feature flags |
scrybe [PATH] |
Bare invocation with a path injects open automatically |
On macOS, scrybe open prefers the .app bundle via open -n -a to satisfy
WebKit's bundle entitlement requirements.
Key library helpers (for integration)
| Symbol | Description |
|---|---|
lint_document(doc) -> LintReport |
Programmatic lint used by both CLI and MCP lint tool |
wrap_full_html(output, title) |
Wraps a RenderOutput in a complete <!DOCTYPE html> with CDN tags |
version_string() / active_features() |
Used by scrybe version |
Build and install
# Rust build (produces scrybe binary)
cargo build -p scrybe-cli --release
# Python wheel (maturin)
maturin build -m scrybe-cli/Cargo.toml --release
pip install target/wheels/scrybe_cli-*.whl
# Run tests
cargo test -p scrybe-cli
1 maintainer
Metadata
1 maintainer
Release files for scrybe-cli 0.6.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 | |
|---|---|---|---|
| scrybe_cli-0.6.3.tar.gz | 166.7 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| scrybe_cli-0.6.3-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| scrybe_cli-0.6.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | Python 3 | none | Linux glibc 2.17+ x86-64 | Details |
| scrybe_cli-0.6.3-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
Total release size: 15.9 MB
Release files / scrybe_cli-0.6.3.tar.gz
| Download URL | scrybe_cli-0.6.3.tar.gz |
|---|---|
| Size | 166.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
061996f794beecc2b600c0ee55bdbb4a0b928e99298749eb20c1a45bbaac26f6
|
|
BLAKE2b-256 checksum How to use checksums |
81b68cafb6cdac0800fdf3f2945ae2e6533c315f4d341083690b220c2dabc7ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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.
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 Jul 21, 2026.
Transparency logRelease files / scrybe_cli-0.6.3-py3-none-win_amd64.whl
| Download URL | scrybe_cli-0.6.3-py3-none-win_amd64.whl |
|---|---|
| Size | 4.9 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8ea2daacf4fcb8335f5c88a03f1b1bb1b457d8a4c9040c3a4edb03ebd68fbc4d
|
|
BLAKE2b-256 checksum How to use checksums |
29bea1dfe180548074c4c0b2893a84f35d7a840936cb32b7e3e6b27556849859
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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.
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 Jul 21, 2026.
Transparency logRelease files / scrybe_cli-0.6.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | scrybe_cli-0.6.3-py3-none-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.7 MB |
| Tags | Linux glibc 2.17+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
a50fdde5185682567bfc3111c44ce0901de708c6b8591d5159ef5fe13a7d653a
|
|
BLAKE2b-256 checksum How to use checksums |
7a2d2a83a46cb97ff2d6b2e9d4e646dd5ce2948366a484a0cda2ab956970a44c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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.
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 Jul 21, 2026.
Transparency logRelease files / scrybe_cli-0.6.3-py3-none-macosx_11_0_arm64.whl
| Download URL | scrybe_cli-0.6.3-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.1 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9fd1b66965f110d9709f76ed74c2bf306ecb74e26fb16540285e31284ba18b92
|
|
BLAKE2b-256 checksum How to use checksums |
6cde433c644a839a7844a041e69dc88bb366a342e1c7a842b20ce08e98df97a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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.
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 Jul 21, 2026.
Transparency log
