erkamyaman/rust-anything
- Source
- GitHub
- First trending
- Category
- Coding tools
- GitHub stars
- 3,372
- Main language
- Rust
This page introduces an external open-source repository. It is not an HDATF product.
What it does
rust-anything helps developers migrate source code to Rust while comparing its behavior with the running original. It supports incremental work on command-line applications, HTTP servers and libraries in languages including TypeScript, Python, C, Go, Ruby and Java. Inputs include the original source, runnable workloads and recorded or supplied cases, while outputs include migration plans, binding scaffolds, behavior recordings and mismatch reports. It profiles workloads, generates a bridge so existing callers can reach Rust, and replays the original's results against the new implementation. The developer or coding agent writes the Rust implementation; this tool is not an automatic code translator. A validation gate combines formatting, Rust code checks, tests, implementation checks and replay of recorded behavior. It runs locally with Rust and the original language's runtime, while dependencies may be downloaded and an optional coding agent's model provider has its own data policy. Passing covers only recorded behavior, not unobserved database or network effects, concurrency under load or other platforms, and crossing the language boundary can make small functions slower.
License
MIT Permissive. Commercial use and changes are allowed if the copyright notice is kept.
More in this category
- interfere-inc/landmines
landmines is a collection of Oxlint rules for teams reviewing code written by AI agents or people. It takes source files and rule configuration as input and reports prohibited patterns with guidance on what to change. Its testing rules target dependency replacements, fixed real-time waits, polling without a completion signal, retries and increased timeouts that can hide unreliable tests. It permits observation-only spies and uses MSW, a network interception tool, as the intended boundary for network test responses. The strict MSW rule checks that unhandled requests are explicitly handled as errors or by a supplied handler, rather than silently reaching the network. Separate rules constrain comments, test placement, filenames, package exports and return-type annotations, while selected rules support counted per-file exceptions. It requires Oxlint 1.81 or later and Node 22.18 or later, and the reviewed rules inspect local code rather than calling an AI service. These are syntax-based policy checks, not proof that the implementation is correct or that every disguised mock or timing problem will be detected. - antithesishq/bombadil
Bombadil is a property-based testing tool for developers who want to explore web and terminal interfaces beyond a fixed set of example scenarios. Its inputs are an application URL or terminal program and a TypeScript specification describing correctness properties and generators of possible actions. The browser driver works with DOM-based interfaces, while the terminal driver interacts with programs that read standard input and write terminal output. The engine repeatedly extracts interface state, evaluates properties, chooses an available action and waits for the next relevant state change or timeout. The inspected runner records snapshots, available actions and violations to a trace before applying the chosen action, giving concrete evidence of explored transitions. Browser results can include screenshots and an inspection view, while terminal traces expose the screen states and actions involved. Documented workflows can attempt to reproduce a trace or experimentally shrink a long failing sequence, but reproduction is not guaranteed and shrinking is marked experimental. The manual targets local macOS or Linux use, CI and Antithesis, and useful domain checks still depend on appropriate specifications, reachable test services and any required login setup rather than an automatic proof that the whole application is correct. - clice-io/clice
clice is a C and C++ language server built on LLVM and Clang, with command-line tools using the same engine. A master process holds document state and schedules isolated compilation workers instead of compiling within the server itself. Stateful workers retain parsed open files, while stateless workers handle one-shot work and background indexing. The project also supports C++20 named modules, compilation contexts for headers and a persistent index. Its query interface reads that index and returns structured JSON for definitions, references, call graphs and file dependencies without requiring a running editor server. Projects normally provide compile_commands.json, and the README lists Linux, macOS and Windows on x64 and ARM64. Index queries describe saved disk content rather than unsaved editor buffers, and stale entries can be omitted unless the index is refreshed. Process isolation does not impose a memory bound on foreground work, and initial project loading can finish without displaying startup progress. - aws/aws-emulator
AWS Emulator gives developers a local AWS API endpoint for testing applications without creating real AWS resources or requiring an AWS account. Applications send ordinary CLI or SDK requests to emulated services and receive responses backed by local resource state. Server mode exposes an endpoint without a graphical interface, while the inspected Rust embedded facade supplies an SDK HTTP client and creates a fresh in-memory engine for each emulator instance. Linux packages provide a server route, Windows and macOS use the documented container route, and embedded Rust tests require compiling the emulator. A full source build requires Rust, a C compiler and substantial build storage, with the README specifying at least 100 GB for the build directory. Resources are temporary, compatibility varies by service and operation, and release fidelity information must be checked against the application's actual calls. AWS explicitly says this is neither a production service nor a security test environment, and executed function code is not isolated from the host user. Usage telemetry is enabled by default with opt-out controls, and this review inspected documentation and source without running service compatibility tests. - github/gitignore
GitHub's gitignore repository is a curated collection of file-exclusion templates for developers using Git, not an AI service or a repository-cleaning program. GitHub uses this collection in its repository and file creation template selectors. Root templates cover common languages and technologies, Global templates cover editors and operating systems, and community templates cover more specialized tools or older versions. A developer selects and adapts patterns for a project, and Git then uses those patterns to decide which otherwise untracked paths to leave out of normal tracking operations. The inspected Node template covers dependencies, caches, build outputs and environment files while allowing an example environment file, and the Python template includes virtual environments, bytecode and notebook checkpoints. Project-wide rules can be shared in a .gitignore file, while personal editor rules can be kept in a separate global exclusion configuration. Already tracked files are not removed by adding an ignore rule, and negation rules cannot rescue a file inside an excluded parent directory without fixing the parent rule. These templates do not detect secrets or remove leaked content from history, and broad exclusions can hide material that a project actually needs to preserve. The collection is offered under CC0, but choosing the correct rules and deciding which lockfiles or generated artifacts belong in version control remain the developer's responsibility.
Only repositories in the ranked Trendshift lists are included, and the lists are used only to find candidates. We do not copy their ranks. Descriptions, licenses and star counts come from each GitHub repository. The notes are our own reading. We have not tested these projects, and a place on a trending list does not prove quality.