How paiml/depyler works
Project type and purpose
• Depyler is an open-source, Rust-based Python-to-Rust transpiler tool and library with CLI, HTTP server, LSP server, formal verification, energy-efficiency optimizations, and a web-based playground. It consists of multiple Cargo crates for core functionality, analysis, verification, Ruchy target, WASM packaging, CLI, and an interactive TypeScript/React front-end.
File structure
• Top-level workspace (Cargo.toml) with sub-crates under crates/:
• depyler-core: pipeline (AST→HIR→optimizer→codegen)
• depyler-analyzer: complexity metrics
• depyler-verify: contract & memory safety checks
• depyler-mcp: Model Context Protocol server/transport
• depyler-ruchy: Ruchy script target
• depyler-wasm: WASM bindings for browser usage
• depyler-quality: CLI commands around quality checks
• depyler (top-level crate): CLI entrypoint and multi-mode server (HTTP, LSP, interactive)
• A playground/ directory holds a TypeScript/React web app, WASM runner, Deno tasks, Docker compose, Nginx config.
• CI/CD workflows in .github/workflows/, release scripts in scripts/, benchmarking in benches/, integration tests under tests/.
README for additional insights
• Multi-target support (Rust, Ruchy, WASM)
• CLI, HTTP server, LSP server, MCP server modes
• Emphasis on testing (property, mutation, fuzzing), profiling, documentation generation
Detail & granularity
• Crate or logical service as its own component
• Versioning or environment details (e.g., Docker container, node/Deno)
• Don’t omit the playground – show how the WASM module interacts with the core
• Optionally, add an inset for the CI/CD pipeline showing build → test → release