# Fix list: AutoIt From Anchor Terminal's listing at https://www.anchorterminal.com/tools/autoit, the October 2026 research run, assessed 14 October 2026. Grade D, 46.3 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on AutoIt: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Security & auth, 20 out of 100, up to 14 more on the total Why it scored 20: No credential model. Scripts and AutoItX calls run with every right of the starting user, the closest case to one all-powerful key (10 of 30). No read-only mode or confirmation step. Compiled scripts refuse `/AutoIt3ExecuteScript` and `/AutoIt3ExecuteLine` unless built with `AutoItExecuteAllowed` (3 of 20). Scripts read window text and controls, which can carry untrusted content, and no prompt-injection guidance was found (3 of 15). No audit log (2 of 15). No security.txt (404), no disclosure policy and no advisories were found on the pages read (2 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 2. Reliability, 59 out of 100, up to 8.2 more on the total Why it scored 59: Read with the local-software lines, since the owner runs the interpreter or AutoItX. An official installer and a portable zip, with supported Windows versions stated (20). No public CI or test suite could be found for closed source. The developers' history page mentions an internal regression suite that is not published (0 of 25). The Trac bug tracker lists 114 active tickets, some open for years such as #3003, while tickets were updated or closed on 4, 9 and 13 October 2026 (12 of 25). A history page per release and a separate script-breaking changes page. Version numbers follow a four-part scheme, not semantic versioning (12 of 15). 3.3.18.0 is a release build on a line in use for years (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 3. Agent ergonomics, 51 out of 100, up to 8 more on the total Why it scored 51: The command line adds no tool definitions to context, and output is whatever the script writes with `ConsoleWrite` (15 of 25). Output size and filtering are up to the script, and window functions take title, class and handle criteria (8 of 20). `/ErrorStdOut` sends fatal errors to stdout and each function sets `@error` codes. Errors do not raise, so an unchecked failure passes silently (13 of 20). Keystrokes and clicks cannot be safely retried, with no dry run (4 of 20). `/AutoIt3ExecuteLine` runs one line without a file, and AutoItX adds a C# assembly, PowerShell cmdlets and a COM control (11 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 4. Schema & documentation, 52 out of 100, up to 7.8 more on the total Why it scored 52: Graded as a scripting language driven from the command line. No machine-readable contract (0 of 25). No llms.txt found, and the documentation is HTML (0 of 10). Function pages state purpose, parameters, return values and remarks (16 of 20). Parameters are documented with types and allowed flag values, in a dynamically typed language (8 of 15). Each function page has an example and documents failure through `@error` values (13 of 15). Dated history for every release and a script-breaking changes page (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 5. Maintenance & community, 20 out of 100, up to 7 more on the total Why it scored 20: Last release 3.3.18.0 on 7 September 2025, more than 180 days ago (0). No release in the last 90 days. Betas sit under a path robots.txt disallows, so were not counted (0). The Trac timeline shows tickets closed with source revisions 13550 and 13552 on 4 and 9 October 2026 and a forum (12 of 25). AutoItX ships in the official package. The NuGet copies are third-party and AutoItX.Dotnet stopped at 3.3.14.5 in 2019 (5 of 15). No public CI or dependency information (3 of 10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 6. Payments & pricing, 60 out of 100, up to 5 more on the total Why it scored 60: Read with the self-hosted rule. Freeware with nothing to buy, so 20 + 20 + 20. No x402, MPP or L402 (0 of 40). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 7. Transparency & trust, 57 out of 100, up to 3.8 more on the total Made of editorial 45, provenance 69. Why it scored 57: The editorial half. Closed source under a clear freeware end-user licence agreement that allows commercial use and forbids reverse engineering (15 of 30). The privacy policy covers the websites and names Google advertising and analytics, and nothing states what the software does with data (10 of 30). The script-breaking changes page and notes on the last versions for older Windows give dated notice of changes, with no deprecation policy (12 of 20). No telemetry statement for the software, and closed source cannot be searched (8 of 20). The provenance half is computed from the provenance block. The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Terms of service: read, states 3 of the 7 things a reader expects (6.6 of 10) - Privacy policy: read, states 4 of the 8 things a reader expects (7 of 10) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: beta builds and their dates, which sit under /autoit3/files/beta/, a path robots.txt disallows - unchecked: AutoItX's own documentation, which was not found at a public URL - Whether the interpreter sends any data over the network could not be checked, because the source is closed ## Weaknesses - Closed source under a licence that forbids reverse engineering - Last release 3.3.18.0 on 7 September 2025, three years after 3.3.16.1 - Windows only, and scripts act with every right of the user who runs them - No security policy or security.txt was found, and no public CI or tests - 114 active tickets on the bug tracker, some open for years ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Pass `/ErrorStdOut` so a fatal error reaches stdout instead of a dialog - Use `ConsoleWrite` for output an agent can capture, since `MsgBox` blocks an unattended run - Check `@error` after each call. Functions report failure there, not by raising - Install the official package from autoitscript.com. NuGet copies of AutoItX are third-party repackages ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.