Lexidown
Fast native HTML-to-Markdown for Python, compatible with Turndown.
Lexidown brings Turndown's conversion behavior, options, and extensible service API to Python. Its Cython conversion engine and bundled Lexbor C parser require no runtime dependencies. Joplin's GitHub Flavored Markdown (GFM) rules are included as an optional preset.
Performance
Across eight complete HTML pages, Lexidown was 4.29× faster than JavaScript Turndown on the Linux laptop and 3.13× faster on the Windows desktop, with identical output. These are geometric means for this corpus. Lexidown's absolute conversion times were lower on the desktop for every page.
Benchmark tables and timings: Linux laptop (Intel Core i7-1260P) vs Windows desktop (AMD Ryzen 7 9700X)
Machines and method
| Linux laptop | Windows desktop | |
|---|---|---|
| CPU | Intel Core i7-1260P | AMD Ryzen 7 9700X |
| OS | Arch Linux, kernel 7.2.3, glibc 2.44 | Windows 11 Pro, build 26200 |
| Python / Node.js | CPython 3.14.7 / Node.js 22.23.2 | CPython 3.14.7 / Node.js 22.23.2 |
| Timed samples per page/converter | 21 across 3 fresh-process rounds | 42 across 6 fresh-process rounds (two complete passes) |
Measured on 10 September 2026 using the same source build inputs, saved HTML snapshots, converter versions, and default settings. Each round uses five warmups and seven measured conversions per page/converter. Conversions run serially; timing includes service construction, parsing, and Markdown conversion, while excluding process startup, file reads, and output hashing. Desktop medians pool both complete passes; no samples were discarded.
The CPU, OS, and build environment differ, so these results cannot isolate an OS effect. The desktop ran Lexidown 1.26× faster and JavaScript 1.72× faster overall. JavaScript's larger improvement explains why Lexidown's lead over JavaScript fell from 4.29× to 3.13× even though Lexidown itself ran faster. These measurements do not establish whether the laptop thermally throttled.
Converter comparison
All speed ratios are geometric means across the eight pages. "Vs JS" compares with JavaScript on the same machine. "Desktop vs laptop" is laptop time divided by desktop time; above 1 means the desktop was faster overall. Individual pages can behave differently. Exact JS output counts apply to both machines.
| Converter | Linux laptop vs JS | Windows desktop vs JS | Desktop vs laptop | Exact JS output |
|---|---|---|---|---|
| JavaScript Turndown | 1.00× | 1.00× | 1.72× | 8/8 |
| Lexidown | 4.29× | 3.13× | 1.26× | 8/8 |
| html2text | 1.17× | 0.84× | 1.24× | 0/8 |
| markdownify | 0.63× | 0.53× | 1.45× | 0/8 |
| markdownify + lxml | 0.81× | 0.64× | 1.38× | 0/8 |
| html-to-markdown | 4.52× | 3.25× | 1.24× | 0/8 |
| html-to-markdown, no metadata | 4.71× | 3.37× | 1.23× | 0/8 |
| fast-h2m | 3.75× | 2.51× | 1.15× | 0/8 |
The converters produce different Markdown; speed and exact-match counts are not quality scores. markdownify + lxml also produced slightly different output between machines on the MDN page; the desktop report records that difference.
Absolute conversion times
Median milliseconds per complete page; lower is faster. Laptop means Linux/i7-1260P; desktop means Windows/Ryzen 7 9700X.
| Page | Laptop Lexidown | Desktop Lexidown | Laptop JS | Desktop JS |
|---|---|---|---|---|
| python-functions | 29.66 | 21.53 | 65.18 | 45.55 |
| whatwg-parsing | 73.94 | 53.82 | 194.63 | 114.31 |
| wikipedia-world-war-ii | 79.87 | 65.99 | 214.48 | 144.49 |
| mdn-array | 9.31 | 7.49 | 20.51 | 14.01 |
| github-cpython | 8.13 | 6.74 | 27.85 | 18.07 |
| guardian-world | 9.71 | 8.56 | 32.51 | 19.77 |
| gutenberg-pride-prejudice | 25.66 | 21.77 | 552.99 | 244.26 |
| rust-book | 184.34 | 136.45 | 2497.99 | 977.48 |
For example, the Rust book took Lexidown 184.34 ms on the laptop and 136.45 ms on the desktop. JavaScript improved from 2497.99 ms to 977.48 ms on the same input.
The corpus focuses on large, complete pages (about 240 KiB–2 MiB of HTML), rather than small snippets. Results depend on page structure, enabled plugins, CPU, OS, power settings, and background load. Full timings for all converters, versions, methodology, and raw samples are in the Linux laptop report and Windows desktop comparison.
Lexidown also matches Turndown byte for byte across all 104 page/option combinations in the compatibility benchmark.
Installation
Requires Python 3.10 or newer.
python -m pip install lexidown
Platform wheels contain the native conversion engine and Lexbor. Installing a matching wheel requires no compiler, Cython, Node.js, or separate HTML parser. For platforms without a matching wheel, see building from source.
Usage
from lexidown import TurndownService
service = TurndownService({"headingStyle": "atx"})
markdown = service.turndown(
"<h1>Hello world!</h1><p>Made with <strong>Python</strong>.</p>"
)
assert markdown == "# Hello world!\n\nMade with **Python**."
To discard scripts and styles along with their contents:
service = TurndownService().remove(["script", "style"])
assert service.turndown("<style>p { color: red }</style><p>Hello</p>") == "Hello"
Like Turndown, the default conversion retains the text inside unsupported tags. Inline styling attributes do not appear in converted Markdown.
For a runnable example comparing default output with custom formatting, HTML cleanup, and a strikethrough rule, see examples/formatting.py. After installing Lexidown, run it from the project directory:
python examples/formatting.py
Bundled plugins
Two presets are included in the normal installation:
from lexidown import TurndownService
from lexidown.plugins.firecrawl import firecrawl
from lexidown.plugins.joplin_gfm import gfm
service = TurndownService().use(gfm) # or .use(firecrawl)
| Plugin | Provides |
|---|---|
gfm |
Tables, task lists, strikethrough and highlighted code blocks |
firecrawl |
GFM plus Firecrawl-style inline links |
See GFM compatibility and table options for details.
Options
Pass a dictionary to TurndownService. Option names and defaults match
Turndown 7.2.4.
| Option | Default | Alternatives |
|---|---|---|
headingStyle |
"setext" |
"atx" |
hr |
"* * *" |
Thematic break text |
bulletListMarker |
"*" |
"-", "+" |
codeBlockStyle |
"indented" |
"fenced" |
fence |
"```" |
"~~~" |
emDelimiter |
"_" |
"*" |
strongDelimiter |
"**" |
"__" |
linkStyle |
"inlined" |
"referenced" |
linkReferenceStyle |
"full" |
"collapsed", "shortcut" |
br |
" " |
Text inserted before a line-break newline |
preformattedCode |
False |
True |
Advanced options
blankReplacement, keepReplacement, and defaultReplacement accept callbacks
with (content, node, options) arguments to customize blank elements, kept HTML,
and elements without a matching rule. options is a dictionary. Callbacks may
omit unused trailing arguments.
The rules option accepts an ordered dictionary of rules to replace the
built-in rule set.
Methods
turndown(html_or_node)
Convert an HTML string or DOM node to a Markdown string. A service can be reused for multiple conversions.
addRule(key, rule)
Register a conversion rule. add_rule is also available as a Python-style alias.
service = TurndownService().addRule(
"strikethrough",
{
"filter": ["del", "s", "strike"],
"replacement": lambda content: "~~" + content + "~~",
},
)
assert service.turndown("<del>old</del>") == "~~old~~"
keep(filter)
Preserve matching elements as HTML:
service = TurndownService().keep("ins")
assert service.turndown("<ins>new</ins>") == "<ins>new</ins>"
remove(filter)
Discard matching elements and their contents. keep and remove accept the
same filters as rules. Added and built-in rules take precedence over both;
use addRule to override an element that already has a conversion rule.
use(plugin)
Apply a plugin function, or a list of plugin functions. Plugins receive the service and can register rules or change options:
def strikethrough(service):
service.addRule(
"strikethrough",
{"filter": "del", "replacement": lambda content: "~~" + content + "~~"},
)
service = TurndownService().use(strikethrough)
assert service.turndown("<del>old</del>") == "~~old~~"
addRule, keep, remove, and use return the service for chaining.
JavaScript plugins need to be translated into Python functions.
Extending with rules
A rule is a dictionary containing:
filter: a lowercase tag name, a list of tag names, or a callback taking(node, options)and returning whether the rule matches.replacement: a callback taking(content, node, options)and returning Markdown.contentis the converted content of the element's children.append(optional): a callback takingoptionsand returning text to append after conversion, useful for reference definitions. Use a closure or bound method to maintain rule state.
Callbacks may omit unused trailing arguments. Rules are selected in this order: blank rules, added rules (newest first), built-in rules, keep rules, remove rules, then the default rule.
Rule callbacks receive DOM nodes with Turndown's camelCase properties, including
nodeName, nodeType, textContent, outerHTML, parentNode, childNodes,
children, firstChild, nextSibling, previousSibling, and getAttribute.
Conversion also exposes isBlock, isCode, isBlank, and
flankingWhitespace (a dictionary).
Escaping
Text is escaped to prevent Markdown syntax from changing its meaning. Override
service.escape to customize this behavior. Text inside code bypasses escaping.
DOM input
In addition to HTML strings, turndown() accepts native Lexidown DOM nodes and
xml.dom.minidom element, document, and fragment nodes. DOM inputs are cloned
before whitespace normalization, leaving the input tree unchanged.
from xml.dom.minidom import parseString
from lexidown import TurndownService
# minidom parses XML; use well-formed markup when constructing a DOM this way.
document = parseString("<p>Hello <strong>world</strong></p>")
assert TurndownService().turndown(document.documentElement) == "Hello **world**"
Building from source
From a source checkout or unpacked source distribution:
python -m pip install .
A C compiler and Python development headers are required. The build installs Cython automatically and compiles the included Lexbor sources. No parser sources need to be downloaded separately.
See Development for tests, Ruff formatting, benchmarks, implementation details, and wheel builds.
Development details
Turndown was ported to Python and optimized using Codex + GPT-6 Astra Ultra.
License
Lexidown's conversion code is MIT licensed, with Turndown's original
credits retained. Bundled Lexbor is Apache-2.0 licensed and includes BSD-2-Clause
components. Their licenses and notices are included in source distributions and
wheels; the combined package expression is MIT AND Apache-2.0 AND BSD-2-Clause.
See third-party notices and Lexbor's provenance and modifications.
1 maintainer
Metadata
1 maintainer
Release files for lexidown 0.2.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 | |
|---|---|---|---|
| lexidown-0.2.1.tar.gz | 650.8 kB | Details |
Built distributions (wheels)
Total release size: 55.9 MB
Release files / lexidown-0.2.1.tar.gz
| Download URL | lexidown-0.2.1.tar.gz |
|---|---|
| Size | 650.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ab6457e9715171335c182d2c9f622856d09de5a1cbbe4df925bcf4055601c89
|
|
BLAKE2b-256 checksum How to use checksums |
8980a704c7c51bc40679cf739ac364b4615f38983e92e6c1c88a5eeada756173
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-win_amd64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 360.9 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0399820cd4ebdcfec9437368a061b992dac0153b7cc86fd412d7a06862c11529
|
|
BLAKE2b-256 checksum How to use checksums |
9e0a14fc834ebfb9bb75324fb716a30d355b7f4328cc2f7509d2a740a685743e
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
72f8155ce32d2edf41c36e84a5eaa02a6645fdeb0045a0e7c597d0ea779cd51f
|
|
BLAKE2b-256 checksum How to use checksums |
34943b031b5a505832c2788000777b3bf15adda4e1fab0ac36d3608cdf8181d2
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
b93f4ddd3ba3a3ab6050c7b91b715ba27a253733be3fadb2445351ddabacb2bb
|
|
BLAKE2b-256 checksum How to use checksums |
7b2ce58e499f54cc93cd0fbfcdedf63de2cf30e23b06343501e115f70e14d037
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
4a60a13cdb2f203e483f9221011b7f6e49e8d2df4704939b0499c04991c3416c
|
|
BLAKE2b-256 checksum How to use checksums |
aa5bf35e4e30d6565e6879c46a3cc02e54cbe9bf11fa3d3edec78771d3d5ce75
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e5544b02c008ff953bde39842874cef0a9987a892058b3610125c8ebc3487d9c
|
|
BLAKE2b-256 checksum How to use checksums |
572c0f40bda5702ca6f83fc596523bbf321a898498dc4d6bf44f26dbc42b2bca
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-macosx_11_0_x86_64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-macosx_11_0_x86_64.whl |
|---|---|
| Size | 493.0 kB |
| Tags | CPython 3.14 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
4488cb64220e37dffa287a15850c9fd7ba6915f6ac0a25a62bc0a993b07a0ede
|
|
BLAKE2b-256 checksum How to use checksums |
2de937a44b7ebdf6b0c230ab913af4a12a5e4a57ab830e6cbd7bc67dc3530143
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | lexidown-0.2.1-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 446.4 kB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
adcbd1fe3b210cb297e4c5da6af8f87072ad5d7445c87ac2fb53ae05e08a0392
|
|
BLAKE2b-256 checksum How to use checksums |
a564da17b553c9be1413dafbb6f41028e7a7a6f5b83c99aac8a753c0fd53753a
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-win_amd64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 356.1 kB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0b9a6b08c9a57c2d6267714f3b39a8ec829b8c07324f69faadcd10008f088a0a
|
|
BLAKE2b-256 checksum How to use checksums |
838f3ce63bdd175b0e68a4e104099a354da51ba14e24e8cda948f6bf981306f0
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
c6e88ff72fb1e67b52de7ca06ed54ea951940beb826a021e960d51b5497355d9
|
|
BLAKE2b-256 checksum How to use checksums |
14ae9d4fe9f64467682b360235873d4322ba4a6e614122822072efb7f73b45a6
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
5b44bbc22e9f09ece965693b36e3a4a7fb01500888e69acce47f08b27a71ab99
|
|
BLAKE2b-256 checksum How to use checksums |
8c60a4405495895e822b1170f5b6b34ceaacd4a6224faa2672e0a5003d0ff6d9
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
54b2a43b831ebd6ae32d6a3752cb2479af2b315c27e5bca591405d5c516a08f6
|
|
BLAKE2b-256 checksum How to use checksums |
ad1342668fba0c79aff0cad498906f46a3dc9c15ff3a54226a007b84f608359a
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7424598200ad1d9b716095f08674411a5085f25b24a420dbf093b6f48ac28fc9
|
|
BLAKE2b-256 checksum How to use checksums |
9f2f993b2dfaae13f0a8a155cff4465a90c9028cb55fa41ffcf3c8639af25ff0
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-macosx_11_0_x86_64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-macosx_11_0_x86_64.whl |
|---|---|
| Size | 490.8 kB |
| Tags | CPython 3.13 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
bce8b2d94804bf8a5568e8ce22624b269366476e822041b9760b5837bacd97f1
|
|
BLAKE2b-256 checksum How to use checksums |
11f4d961dedda3f3047c6c130a75851f0f108ab825c9407fb648c50cd9b4df16
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | lexidown-0.2.1-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 444.1 kB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
58df6f7bca0b8066dda89fb7a944eb93183e44855c569506435a33ff86f5f9a7
|
|
BLAKE2b-256 checksum How to use checksums |
59e124360f7c4977864b39a3a4e89f10e83d8d8a8dbfaf0c11d67381728ca3c5
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-win_amd64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 356.1 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
2021b20dec85badbe892013e69b92e428103a84b64682a5a5e971a2f4ced5c9f
|
|
BLAKE2b-256 checksum How to use checksums |
bf5e6fe854b7ae74f7531f54a7df12f00adad908b4f321d0bad2e8a09488de57
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
17c53ae825009033aa72075502b6ac1b86fe5244334d768964db47393bfa92e3
|
|
BLAKE2b-256 checksum How to use checksums |
eab214fc4216167639811fc0676f1dab0cd15b1c661ab2c54368367bb1350d81
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
1ad771fce6bdc1db2ed0152e061c7e764d36521aea845e338001a35078bda64a
|
|
BLAKE2b-256 checksum How to use checksums |
49ae0b7671a634a1623787b6ddd71655a3e8f61fe900059c165ab110874d7b3b
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9baa8ca4c55eb3f4b827d6a26d64922d249b1c3be72a0525d5972dbb7497633b
|
|
BLAKE2b-256 checksum How to use checksums |
7b264c7ce1eb134a193c966ae482d337c7d339c2862d00fc3f7853946960fbf9
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
1f7baf2462a71ff24a7b4bcc978a48360aacabf76427dbd3b117916c99d2e679
|
|
BLAKE2b-256 checksum How to use checksums |
bcb4ca7f4d0db7fb06a785ce3d46751ba336a27f25b6f6f2ef4811b9db300103
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-macosx_11_0_x86_64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-macosx_11_0_x86_64.whl |
|---|---|
| Size | 492.3 kB |
| Tags | CPython 3.12 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
032a3acd17f31316ca571bddb6dc312a74cc8dee62c16f60ba2a6ad2e19d0be9
|
|
BLAKE2b-256 checksum How to use checksums |
dec0cca20331ae7bd6b831f6329f12cc10aa96971b204eb64f0d9b1a05c1c996
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | lexidown-0.2.1-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 446.7 kB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
52269d9128f49f2b495a26e21277ddedabe5e5212b9495d74be166eb2023edd5
|
|
BLAKE2b-256 checksum How to use checksums |
23273da96e5773e383099f314e8a056da676884e332ff51890214bcdf8a54cf9
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-win_amd64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 367.2 kB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b634110ea3c4c7ad6e71247048939d8d675e4a1bfed841c196325faf9e7d65a9
|
|
BLAKE2b-256 checksum How to use checksums |
ba0b314690dafefec8826c6d3ad68f790ba9fd34509da640ac414bea10601fdf
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
071072c53c096c2e27a1220a3cb3715130f47ff55857219e8160989f38b43eb9
|
|
BLAKE2b-256 checksum How to use checksums |
f576f30a59721a5684ceb5ae554b9fb948269994e7f8b17a3cd794096f0e51c7
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
91d23e7c1c9538ee63d9b28fa93a470128a583d359c1236f7feed0059859b5ad
|
|
BLAKE2b-256 checksum How to use checksums |
bad99d893f57804ae54d0c1b69295d8263d7d7c4398adabc8ae3859564cd0f45
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
15b59dd203e1826312b725c1f2e07bee4fda42d5930e059b455f0987f5d85747
|
|
BLAKE2b-256 checksum How to use checksums |
2a098ab50268a04087f50087449d610c65bb061b536f3ce46a06bfc019bdc5e0
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
38d78d64a81ff375564b0c82d30f6a70bb5bf53ff6593f2ac4fa69069dd2f769
|
|
BLAKE2b-256 checksum How to use checksums |
b6381fa8dd014f79ed6140b407cf4e77e77bc44d838df0e0868709f62e40d591
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-macosx_11_0_x86_64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-macosx_11_0_x86_64.whl |
|---|---|
| Size | 492.7 kB |
| Tags | CPython 3.11 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
daa1ef1257b0a67d5dd5092277a26778f5834f8bac0e5bf9b5bb171756164404
|
|
BLAKE2b-256 checksum How to use checksums |
c08ba112e67a5d66b01ddee9c448b0d6f6361957f9fd18654012ba57f8189c42
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | lexidown-0.2.1-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 450.3 kB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
233edeac84d385be69cd3e8144db1f7362a312eadd5ee832f860c0101538114f
|
|
BLAKE2b-256 checksum How to use checksums |
3882050c73c8265f15038424af02604210bd46c292a285003cffd82ef176f689
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-win_amd64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 366.0 kB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
f002282f04be0b89008be03c70a82cbe3d6c7a7abb86e4cbda0ee1093481cbf3
|
|
BLAKE2b-256 checksum How to use checksums |
41d66ee81b5c4ad50bd6bcb22dac9dce7661eec5816bac09d1ce6fdf5307aea5
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
626236032d510cdc0139e4101fb52f52d6e34ff903bc7670e0ada7b60f7a178f
|
|
BLAKE2b-256 checksum How to use checksums |
4bd6c0a249d8c1f11a459c4635e8f4975fd29ecb0de9a46da4cabe9c7ba1512b
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
d7bc74ed1f30360a8893d1690dce08873878c415cb99c1a4998e3feef494680c
|
|
BLAKE2b-256 checksum How to use checksums |
a7a3e9e74d1fe6066257f3032ba6176cdcf33a1f67e1d58fa0ed8d3a58805ad9
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
698cfe33aa62e2a767520f9e45a14571b03c27a281be7db31066023d32269fbb
|
|
BLAKE2b-256 checksum How to use checksums |
edff503a48df1327a0fe935966a8de43290cd39e7273c17d682123f8312bc966
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
e6633fd01d3ef611265783f6e912d9cfbe794681b44bf36bb0e03bdbab4d3c21
|
|
BLAKE2b-256 checksum How to use checksums |
04e62813652d56a3c8cdf845ff5d413723fac499ae4f4f544765b02d2b378a03
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-macosx_11_0_x86_64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-macosx_11_0_x86_64.whl |
|---|---|
| Size | 493.4 kB |
| Tags | CPython 3.10 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
2465ba81687569d90bc5a05eaaa662baeade29dd4e6381df6c4792cfe2245278
|
|
BLAKE2b-256 checksum How to use checksums |
b6e58c5e0d44bd7ab0bbf8d6ccd21c70e0eb0f493b0ea914e69b455c633dba7a
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency logRelease files / lexidown-0.2.1-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | lexidown-0.2.1-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 451.3 kB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
158b07bc4fc05ad2ba25700e19d65c88be92e449590f4b116e6ec641ada63473
|
|
BLAKE2b-256 checksum How to use checksums |
913bbb84234bbf31b39a4b4581e4c354624192f8fa60888655fd270b3e6e1c5b
|
| Upload date | |
|
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.
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 Sep 10, 2026.
Transparency log
