All notable changes to EdgeParse are documented here.
The format follows Keep a Changelog and this project adheres to Semantic Versioning.
- Separate benchmark groups for
non-ocrandhybridruns so published comparisons can be reported more cleanly - Shared benchmark snapshot data for the site so landing and docs stay aligned from one source
- Bumped the workspace and published SDK manifests to
0.2.2 - Rebuilt the checked-in WASM package used by the demo and site so browser deployments use the latest parser bundle
- Updated the site/demo release path to ship the refreshed WASM bundle and current benchmark documentation
- Disabled WASM npm publication while keeping the release tarball attached to GitHub Releases
- Corrected benchmark runner/docs grouping so hybrid engines no longer appear under the non-OCR bucket
- Dedicated
release-wasm.ymlworkflow to publishedgeparse-wasmon tagged releases and attach the npm tarball to the GitHub Release - CI coverage for the WASM target and Docker image smoke builds so every shipped artifact is validated before release
- Release-channel documentation in the README covering crates, SDKs, CLI archives, Homebrew, and container images
- Bumped the workspace and published SDK manifests to
0.2.1 - Local release helpers now publish
pdf-cosbeforeedgeparse-core, matching the crates.io CI workflow make publish-allnow includes the WASM SDK release path- README benchmark results updated to the latest 200-document
opendataloader.orgcomparison, where EdgeParse leads the published field on every reported metric
- Removed stale release documentation that still described five workflows and partial manual workarounds for older releases
- Updated install guidance to reflect Linux
glibc >= 2.17compatibility for release binaries
- WASM SDK (
edgeparse-wasm): WebAssembly bindings for browser and edge-runtime deployments - WASM demo (
demo/): Interactive in-browser PDF extraction demo using the WASM SDK - Enterprise page on the website (
/enterprise) with pricing and contact CTA - Contact page on the website (
/contact) routed from all enterprise CTAs - Demo link in the site header and landing page hero section
- Elitizon partnership links across the site
- Social-card meta tags, Open Graph images, and sitemap improvements for SEO
- Cross-compilation for Windows CLI binary now uses
cargo zigbuildcorrectly (no spurious glibc suffix on Windows targets) - Trivy security-scan action pinned to
v0.35.0(was@master) and uses the correct image tag (stripsvprefix) edgeparse-coreinternal dependency version constraint updated to0.2.0
- CLI release workflow: Windows cross-compiled binary no longer received a Linux glibc suffix (
.2.17) which could causecargo zigbuilderrors - Docker release workflow: Trivy scan now pulls the correct image tag (
0.2.0, notv0.2.0)
- Zero Clippy warnings across all crates
- Corrected
.gitignoreto exclude build artifacts cleanly
- Comprehensive Rust doc comments on public API surface
- Step-by-step tutorials for CLI, Python SDK, Node.js SDK, Rust library, and output formats
- CI/CD publishing guide (
docs/07-cicd-publishing.md)
- Bumped version to
0.1.1in all crates and SDK manifests
- Core extraction engine (
edgeparse-core): Rust-native PDF-to-structured-data pipeline — no ML, no Java, no GPU - Python SDK (
edgeparse): PyO3-based bindings, available on PyPI - Node.js SDK (
edgeparse): NAPI-RS bindings, available on npm - CLI binary (
edgeparse-cli): Zero-dependency binary for all major platforms - Rust library (
edgeparse-core): First-class crate published to crates.io - Reading-order reconstruction for multi-column and sidebar layouts
- Ruling-line and borderless table detection with cell-span merging
- Heading and paragraph classification
- AI safety filters (PII scrubbing, content flags)
- Tagged PDF support (PDF/UA accessibility structure)
- Output formats: JSON (full schema), Markdown, HTML, plain text
- Benchmark suite comparing EdgeParse against Docling, Marker, pymupdf4llm, MinerU, MarkItDown, and LiteParse
- Docker image for containerised deployment
- High-level technical documentation: overview, architecture, pipeline, data model, extraction, output formats, SDK integration
- GitHub Actions CI workflows for Rust, Python, Node.js, and Docker
- Renamed Node.js package from
@edgeparse/pdf→edgeparse