CLI Runner Terms and Risk Disclosure

Effective date: 13 September 2026 Provider: Kanabe Aron Persoană Fizică Autorizată Address: 692, Sânsimion, Harghita 537285, Romania Tax identification code (CIF): 42879844 Trade Register No.: F19/359/2020 VAT identification number: RO42972799 Email: [email protected] Tool: codingchallenge (the "CLI")

---

---

1. What this covers

These terms govern the CLI specifically, and form part of our Terms of Service. The CLI is optional. You never have to install it.

Everything in these terms is in addition to the Terms of Service, and the disclaimers and liability limits there apply here too.

2. What the CLI actually does

We would rather you understand this than agree to it blindly.

It installs by running a script from the internet. The documented installation is curl -fsSL … | bash on macOS and Linux, or irm … | iex on Windows. This pattern downloads a script from our server and executes it immediately with your user's privileges, without you reading it first. It is convenient and it is common, but it is a meaningful amount of trust. You may download the script, read it, and run it separately instead — we recommend this.

It writes to your working directory. The CLI creates and manages a .codingchallenge/ directory inside whatever folder you run it in, and reads and writes files there and in that folder. It can overwrite or delete files. Files it deletes are gone — not moved to a recycle bin or trash.

It executes definitions our servers supply. When you select a challenge, the CLI downloads a bundle from us — a Dockerfile, a Docker Compose file, and test scripts — and writes them into your working directory. When you run a build or test, it executes those files on your machine. You are running code we sent you.

It runs Docker containers. The CLI shells out to Docker Compose. It builds images, starts containers, binds network ports on your machine, and consumes CPU, memory, and disk. Docker itself typically runs with elevated privileges on your system.

It updates itself. The CLI checks our server for a newer version, downloads a new binary over the network, and replaces its own executable on disk. This can happen without you explicitly asking for an update.

It stores your login token on disk. Signing in stores an authentication token in a file on your machine. Anyone with access to your machine or your files could use it to act as you on the Service. Run codingchallenge logout to remove it.

It talks to our servers. To authenticate, fetch challenges, download bundles, upload submissions, and check for updates.

3. Known limitations you should weigh

We would rather tell you these than have you assume otherwise.

• Downloads are not cryptographically verified. The CLI does not currently verify a signature or checksum on the binaries it downloads during self-update, and the install script is not pinned to a specific version. If our distribution server or the network between you and it were compromised, the CLI could download and execute something we did not publish. We intend to add signature verification; it is not there today.
• Bundle contents are not sandboxed on your machine. The Dockerfiles and scripts we send you run with whatever privileges you give them. The isolation that protects our infrastructure does not exist on yours.
• We cannot test every environment. The CLI runs on your operating system, your Docker installation, and your configuration. Interactions we have not anticipated are possible.

4. Use it safely

Strongly recommended:

• Run it in a directory you can afford to lose. A dedicated folder for challenge work — never your home directory, a repository with uncommitted work, or anywhere holding data you cannot replace.
• Keep backups of anything that matters, independently of this tool.
• Do not run it as root or Administrator, and do not run it with elevated privileges.
• Do not run it on production machines, on work machines where you lack permission to install software, or on anything holding confidential data.
• Consider a virtual machine or a disposable development container if you want isolation.
• Read the installation script before you run it, rather than piping it straight into a shell.
• Log out (codingchallenge logout) on shared machines.

5. Your responsibilities

• You decide whether to install and run the CLI, and on which machine.
• Your machine, your operating system, your Docker installation, and your data are your responsibility. We have no visibility into and no control over them.
• You are responsible for backups. We hold no copy of your local files and cannot restore anything.
• You must have the right to install and run software on the machine you use.
• Your use of the CLI must comply with our Acceptable Use Policy.

6. Disclaimer and liability

The CLI is provided "AS IS" and "AS AVAILABLE", without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that it will work on your system, that it is free of defects, or that it will not cause loss.

To the maximum extent permitted by law, we are not liable for any damage to, loss of, or corruption of data, files, software, hardware, or systems on your machine arising from downloading, installing, or running the CLI — including files deleted or overwritten by the CLI or by anything it executes, damage caused by containers it runs, and consequences of the self-update mechanism.

The overall limitation of liability in Section 12 of the Terms of Service applies. Nothing here excludes liability that cannot be excluded by law, including liability for fraud, gross negligence, willful misconduct, or death or personal injury caused by our negligence. If you are a consumer, your mandatory rights are unaffected, and nothing here asks you to waive them.

7. Licence

We grant you a personal, revocable, non-exclusive, non-transferable licence to download and use the CLI to interact with the Service, subject to these terms and the Terms of Service.

You may not redistribute, resell, or sublicense it; modify or reverse-engineer it, except where that restriction is prohibited by law; or use it to access the Service in ways prohibited by the Acceptable Use Policy.

We may modify, update, or discontinue the CLI at any time without notice. There is no guarantee that any version will keep working or stay compatible with the Service.

8. Privacy

The CLI sends us your authentication token, the challenge you are working on, and the submissions you upload. It does not scan your machine or collect files you have not submitted. What we do with submissions is described in the Privacy Policy — including that submission files and logs are deleted about 30 days after a submission completes.

9. Uninstalling

Delete the codingchallenge binary from where the install script placed it, run codingchallenge logout first (or delete its configuration directory) to remove your stored token, and delete any .codingchallenge/ directories in your project folders. Docker images and containers it created are removed with the usual Docker commands.

10. Reporting problems

If the CLI damages something, behaves unexpectedly, or you find a security issue in it, email [email protected]. Security reports are welcome and we will not pursue you for a good-faith report — see Section 2 of the Acceptable Use Policy.