Inspect and trust the client
Use this optional reference for release maintenance or a requested security review. Routine diagnosis runs the installed client directly. The downloadable file is readable JavaScript. It needs Node.js 24 or later and no npm installation.
Review this exact release
Build and permission record for 0.21.0 · Artifact hashes · Public package source
The trust-v2 build record binds the independent client, helper and archive hashes to the authored module inputs, build versions and lockfile. A build check rejects bundled npm runtime modules and external imports other than Node built-ins. The website and GitHub release should describe the same bytes. A record or checksum from the publisher is not independent authentication of that publisher.
Ask the client for an offline plan
node client.mjs --plan --profile quick --execution agent-host --output reading.json
This validates the options and prints planned endpoints, payload budgets, timing bounds, OS observation and output effects. It makes no test request, DNS lookup, OS command, publication or file write. Reading a plan does not grant permission to run it. Use --plan --profile extended-v1 to inspect Extended without acknowledgement or effects. A supplied --ack-payload-bytes must match the selected total even in a plan. The option is forbidden with --help, --version, --network-info and --check-publication.
What the process can access
| Operation | Scope |
|---|---|
| Measure | HTTPS requests to speed.cloudflare.com. Redirects are rejected. Quick plans 40 MiB of payload; standard plans 160 MiB. Extended allows up to 2 GiB total, 1 GiB per direction, with the Standard schedule. It requires explicit user authorization for that allowance and --ack-payload-bytes 2147483648. Publication consent is separate. There is no automatic escalation or repeat. Probes and protocol overhead are additional. |
| Coordinate helper and load | On macOS/Linux, authorized measurement temporarily opens three exclusive loopback listeners before helper discovery. Acquisition can add four seconds. No coordination files are written. A running helper settles through authenticated loopback control, which can add another four seconds. An absent helper stays excluded until completed-artifact save. Unreachable existing state blocks load. Help, plan, status and comparison-only commands do not bind these listeners. |
| Observe the host | Fixed route and network utilities, without a shell or administrator access. Inspection can resolve the test hostname. Raw identifiers are excluded from results. Disable it with --no-network-detection. |
| Save | Only when --output is supplied. A new file is required. Completed data is saved before publication. Keep the output in a private directory. |
| Publish | Only with explicit --publish and a location choice. A result may include an approximate area, network hint, optional network facts and UTC day. Tokens are never saved in result files. |
| Compare observations | Opt-in GETs without credentials. Serial 5-second requests within 20 seconds, one 64 KiB context response only when separately authorized and needed, and 1 to 3 pages per scope at 512 KiB each. Comparison-only makes no test, host observation, output reservation or publication. Search hints never change measured location. |
| Check a result | One read-only request for a known result ID. No new test, contribution or local file write. |
Reading or unpacking the plugin starts nothing. It adds no install scripts, hooks or automatic updates. Explicit macOS install can create a per-user login service with separate continuing consent. Explicitly authorized helper enable or install can initialize private SQLite state and a local reporting credential. The helper uses five-second HTTPS opportunities, optional separately consented interface counters and completed-day private reports. Finite probe-only permits carry no reporting credential. Separate public allow, withdraw and reconcile commands control future eligible quality reuse. Inspect their offline plans, current helper status and the packaged permission instructions. Interface traffic is excluded from public reuse. Service gates default closed. A normal Node process has the permissions of its user. These code boundaries are not an operating-system sandbox. Inspecting source and matching publisher hashes do not guarantee absence of malicious behavior. Keep the Node runtime and OS maintained.
Recover without using more test data
node client.mjs --check-publication 00000000-0000-4000-8000-000000000001
Replace the example ID with the one in your saved result. Confirmed means the selected service returned that ID. Not found describes the check time; an earlier request could still finish later. Unknown means the check could not establish an outcome. Keep the original artifact and never automatically repeat a measurement to resolve a publication.
What has been verified
Release checks exercise the actual independent executables and extracted package with local HTTPS, native counter and persistent Worker/D1 fixtures. Local checks do not prove live service availability or installed lifecycle. OS observation tests include recorded platform fixtures; those are not proof of execution on every OS or every host. Your agent should retain the client version, execution host, test quality and publication state when it reports a reading.
The owner reports a successful Grok Bot test and public contribution. That is useful evidence for that run. Codex local installation, a portable ZIP and a Bot run do not establish acceptance by either public marketplace. Publisher identity, eligibility and platform review remain separate. See distribution status.
Report a problem
Open a package support issue with the client version, command flags and sanitized error. Do not include credentials, private files, an IP address or precise location. Read what a public result contains.