anthropics/sandbox-runtime

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

What it does

Anthropic Sandbox Runtime is a CLI and library that restricts file access and networking for arbitrary processes, including agents and local MCP servers. It accepts a command plus filesystem and network policies and executes the command within operating-system boundaries. macOS uses sandbox-exec, Linux uses bubblewrap, and HTTP and SOCKS5 proxies check permitted network destinations. The current README also describes alpha Windows support using a separate account, restricted tokens, file ACLs and WFP network filters. The package requires Node.js 22.12.0 or later, and restrictions apply only when commands are explicitly wrapped or the library is integrated. Linux requires bubblewrap, socat and ripgrep, while Windows requires a separate elevated setup step. Default reads are allowed, so automatic protection of secret files must not be assumed. Read-denied paths, write-allowed paths and allowed domains must be configured for the workload. This is an early research preview, and documented Windows gaps involving alternative tokens and service-mediated traffic prevent treating it as an absolute security boundary.

License

Apache-2.0 Permissive, with a patent grant. Commercial use is allowed; keep the notices and state your changes.

More in this category

• paradigmxyz/iron-proxy
  iron-proxy is an outbound traffic proxy for CI jobs, coding agents and containers that should not have unrestricted internet access. It accepts workload requests and a YAML policy, then forwards permitted traffic or rejects it while producing structured audit events. Its DNS and TLS interception route requests through ordered transforms, including destination allowlists and replacement of placeholder tokens with real credentials held by the proxy. The inspected allowlist implementation rejects unmatched requests unless an explicit warning-only mode is selected. Deployment requires the proxy process or container, configured destinations and secret sources, client trust in its CA, and actual routing through it. DNS configuration alone is not a containment boundary because a workload can connect directly, so separate network enforcement is needed. Optional MCP policy filters tools and arguments over Streamable HTTP, but its documented scope does not cover resources or prompts. Audit body capture and header annotations can expose plaintext, and TLS interception makes the proxy and CA sensitive infrastructure rather than an automatic guarantee against data leakage.
• openai/php2shell-checker
  PHP Version Checker helps website operators identify PHP versions that fall within the repository's php2shell vulnerability ranges. It accepts a website URL or a local PHP executable as input. The URL path reads Server and X-Powered-By response headers, while the local path reads the executable's version output. It compares the extracted version against an embedded table of vulnerable patch cutoffs for each listed branch. Results are OK, VULNERABLE, or UNKNOWN, with JSON output and exit codes available for automation. The repository also provides separate agent instructions for URL-only checks and checks with server access. Direct use requires Node.js, and checking the actual serving build requires access to the relevant server installation. It neither follows redirects nor inspects response bodies, and hidden headers, modified banners, vendor backports, and a different command-line PHP installation can make the result incomplete or misleading.
• Check-Risk-WAF/Check-Risk-WAF
  This repository presents the Check Risk WAF product and its interface assets for inspecting requests before they reach websites and APIs. The public tree centers on a README and images; it was not confirmed as an open firewall-engine source library. Intended users are web-service operators, with HTTP and HTTPS requests and administrator policies as inputs. The product description says a reverse proxy checks requests, forwards allowed traffic to the original application and logs blocking reasons and rules. Its panel configures web-attack filtering, bot checks, request-rate limits and attack-event analysis. An AI feature explains a selected incident and proposes exceptions, but this does not certify detection accuracy. On-premise installation requires an Ubuntu Server 24.04 LTS x86_64 host and an external distribution package, while cloud setup requires registering the domain and upstream and rerouting traffic. Downloading the repository does not enable protection; TLS certificates, upstream routing and real-client-IP forwarding need separate configuration. Deployment variants differ in features and terms, so review commercial-use conditions, data handling and false blocking of legitimate requests.
• hcliucs/APSD
  APSD is the official dataset repository for a 2024 paper in IEEE Transactions on Information Forensics and Security (TIFS). The paper is titled "Stealthiness Assessment of Adversarial Perturbation: From a Visual Perspective". An adversarial perturbation is a small change added to an image to mislead a classifier, and this work studies how visible that change is to people. Its starting point is that metrics such as Lp norms, PSNR and SSIM can disagree with human perception. The dataset holds 10,586 image pairs made from 400 reference images with 12 attack methods in five families, such as FGSM, PGD, CW, AdvGAN and Square. Of 60 observers, 15 rated each adversarial example in two steps, first sorting how visible the change is and then scoring it in detail, and the mean opinion score (MOS) from 0 to 1 is the label. The README also describes A2SM, an attention-based model that predicts these scores, and reports 0.984 PLCC and 0.978 SROCC on APSD. The repository has only four files, the README, two figures and a Google Drive link file, with no attack code and no A2SM model code. The data comes from that Drive link, and the README says the exact folder and file names follow the actual package, so its example tree may differ. The license is still to be decided (TBD), and the README says that if the dataset contains images from ImageNet, COCO or VOC2012, their original terms also apply.
• scrapfly/Antibot-Detector
  A Chrome extension that detects anti-bot systems, CAPTCHAs and browser fingerprinting. It analyzes page elements, network requests and browser APIs, and displays detection results and history.

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.