Yardsort

The security notes say the app launches user-configured programs with an argument list rather than through a shell. Those programs inherit the login-shell environment, and an agent can act within its own permission model, so least privilege is only partly supported. The README and SECURITY.md repeatedly describe confirmation before actions such as closing with work in flight, deletion, merging, closing, or reopening; updates also require user action. Network uses, the update check, optional Assist, and local log scope are described concretely. The app says it stores no credentials, but it uses the user's GitHub CLI login and can use a user-provided Assist key. Dependency security has a frozen-lockfile install process but no evidence of dependency auditing or vulnerability handling. External effects have confirmations and permission explanations, though some actions reach GitHub and other services. Ordinary git worktrees, retained branches, and confirmation before discarding uncommitted changes provide some recovery options; the files do not give a complete restoration procedure. Vulnerability reporting and release notes provide attribution paths, but publisher identity is unverified and maintainer identity cannot be confirmed.

The README and Cargo and package metadata agree on version 0.20.0. CI covers Linux, macOS, and Windows and lists formatting, lint, type-check, and test steps; this supports ordinary consistency, but this review did not execute verification. GitHub CLI and terminal agents are optional or external dependencies. The README documents prerequisites for some features but cannot guarantee those external tools remain available. CI and packaging workflows give explicit messages for timeouts, missing credentials, and some failures; evidence for runtime error handling is limited.

The intended audience, parallel worktree model, supported platforms, built-in agents, CLI, tasks, and workflows are described concretely for developers using terminal coding agents. The security notes state that the app launches configured programs and that agent capabilities depend on their permission model, but the broad feature descriptions do not specify permission boundaries or risks for every feature. Workflows describe triggers and variable validation, and the README lists controls, commands, and prerequisites; the supplied material does not corroborate every operation's trigger conditions. CI has a Linux, macOS, and Windows matrix, providing strong platform-fit evidence.

The README is organized by feature and links to a quick start and topic guides; however, the supplied README truncates in the supported-agents section, limiting assessment of documentation coverage. A quick-start link and download entry are present, but the supplied files do not provide installation steps. Yardsort, ys, and workspace terminology is consistent in the examples, and Cargo and package metadata agree on the version; no changelog evidence is included. Examples cover CLI use, workflows, handoff content, and supported agents; FAQ evidence is limited. The docs identify limits such as log coverage, cost-estimate scope, the GitHub CLI requirement, and security fixes being limited to the latest release. GPL-3.0-only metadata agrees with the GPL v3 LICENSE. Security reporting and release notes provide maintenance paths, but publisher identity is unverified and no specific maintainer responsibility is established.

The product describes outputs including separate worktrees, live file diffs, activity records, handoff messages, and optional workflows that support review and follow-up; the supplied material cannot verify runtime results. It combines parallel terminal agents with ordinary Git workspaces, desktop review, and a CLI, showing a clear additional use. Cost notes distinguish estimated API prices from subscription bills and state that some models have no cost estimate; actual resource use and cost effectiveness cannot be established statically.

The README and SECURITY.md make specific claims about data flows, security boundaries, confirmations, and limitations. Cargo, package metadata, the license file, and CI allow some claims about version, license, and declared checks to be cross-checked. Multiple files corroborate license, platform, and version information, but most product behavior is still described in the README and security notes. The material distinguishes recorded metadata, unknowns, and estimates—for example, handoff content says it does not know the agent conversations—but many features and security guarantees are not demonstrated by implementation files in the supplied evidence, so only partial credit is justified.