aws/aws-emulator

This page introduces an external open-source repository. It is not an HDATF product.

What it does

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.

License

CC0-1.0 Custom or non-standard license. Read the license file before any reuse.

More in this category

• 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.
• zed-industries/zed
  Zed is a desktop code editor for developers who want to edit a project together and work with AI in the same interface. It takes project files and editing requests and produces file changes and agent conversation results. Its collaboration features show participants' cursors and edits in real time and provide voice communication. The editor also hosts external agents through ACP, a protocol connecting an editor to an agent process. External agents generally manage their own runtime, authentication, models and tools rather than inheriting all of Zed's settings. It runs on macOS, Linux and Windows, while a web version is not available according to the README. Collaboration requires signing in, and sharing a project gives collaborators access to files inside that project. Model data handling and tool permissions must be checked separately for the selected agent and provider.
• gauge-sh/gauge-cli
  This developer CLI repeatedly tests whether agents can actually use a product's tools and documentation. It accepts inputs such as Skills, CLIs, SDKs and docs, together with realistic tasks and observable criteria. Outputs retain session transcripts, tool activity, judgments and evidence for improvements. Local mode injects working-tree inputs into fresh Docker sessions and stores evidence and measurements in a private workspace. The user's coding agent writes improvements and analyzes results in local mode. Requirements include Node.js 22.13 or newer, npm, Docker running Linux containers and credentials for the tested agents. The local loop needs no Gauge account, but model usage belongs to the provider account or subscription. Managed execution, automatic analysis and authenticated MCP/API inputs belong to hosted capabilities, with separate identities and storage across modes. Default CLI usage telemetry can be disabled, and web-response fixtures are not complete network isolation, so test data and secret boundaries need review.
• tembo/voxl
  This Rust tool lets a web browser view and control a server or virtual machine desktop. It captures an X11 display on Linux and the running computer's screen on macOS and Windows. The screen is encoded as H.264, sent over a WebSocket and played through the browser's WebCodecs support. It provides mouse and keyboard input as well as clipboard, file transfer and audio features. Agents can use APIs for screenshots, video recording and waiting for screen changes or stillness. The wait implementation tracks changed screen regions and sequence numbers; a still screen does not itself establish task success. Getting started requires a target desktop and platform-specific video and audio libraries, with a protected connection such as HTTPS for remote browser access. It does not create a separate virtual machine, and authenticated viewers can normally control the streamed desktop. The documentation says Wayland and GPU encoding are not yet supported. Its own code is MIT, but the README states that distributed binaries linked with x264, and distributions bundling them, fall under the GPL.
• ivankovic/omnidiff
  OmniDiff compares two files and presents changes according to their content rather than only matching lines. For supported programming languages, it parses syntax trees with tree-sitter and combines subtree matching, residual matching and move recovery to identify insertions, deletions, updates and moves. Images, archives, fonts, translation catalogs and PDFs have content-specific comparisons, while unsupported text uses line comparison and unknown binary content receives a change notice. Results can be viewed in an interactive terminal interface or emitted as plain text or JSON for other tools. Git and Jujutsu integrations require their own configuration, and the JSON format supplies file paths and changed ranges rather than embedding file contents. Linux, macOS and Windows binaries are documented, while building from source needs Rust 1.92 or later and a C compiler. Starting with a pair of local files does not require a model service, and the documented stable integration surfaces are the command line and JSON, not every internal Rust API. Reported performance and accuracy belong to the author's datasets, the stated highlighting accuracy goals are not yet met, and licensing needs review because the README and package declare AGPL with a separate commercial option.

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.