Kodi 21.2 — the first minute without a single click
How we tested: a clean Debian 13 in a disposable container; source — package kodi 2:21.2+dfsg-4 from the Debian repository. Run as a regular user on a virtual screen, 60 seconds, nothing clicked. 18.10.2026. Every network request and every file written was recorded; the code was not decompiled. The container was deleted afterwards.
Program website: https://kodi.tv/
Package SHA-256: 74aa7546d14c64a079e3da90d9263fe3f6fafcb45abee26c3a400254c36f2408
Summary
| What we checked | Result |
|---|---|
| Built-in telemetry, crash reporting, analytics, ad SDKs | none |
| Network requests in the first minute | 7 server names |
| Known trackers among the servers | none |
| Files written in the first minute | 300+ |
| The program ran the whole time | yes — process alive at the end |
What is built in
2089 files (100 MB) were checked.
No code of known telemetry, crash reporting, analytics or ad SDKs was found.
Addresses of known trackers in the program’s files — addresses in code, not requests:
| Tracker | Addresses | Mentions |
|---|---|---|
| YouTube | www.youtube.com | 1 |
Where it connected
| Server | How | From second | Times | Known tracker |
|---|---|---|---|---|
ftp.halifax.rwth-aachen.de | connection | 17.5 | 2 | — |
ftp.snt.utwente.nl | connection | 21.0 | 3 | — |
mirror.karneval.cz | connection | 19.3 | 2 | — |
mirror.math.princeton.edu | connection | 11.7 | 1 | — |
mirror.netcologne.de | connection | 15.6 | 4 | — |
mirror.umd.edu | connection | 22.8 | 2 | — |
mirrors.kodi.tv | connection | 10.3 | 1 | — |
A DNS lookup is not yet a connection: the program looked up the server’s address. But the lookup itself is visible to the ISP and the DNS server.
What it wrote to disk
Folders the program wrote files to during the minute:
| Folder | Files |
|---|---|
~/.kodi/addons | 198 |
~/.cache/mesa_shader_cache_db | 102 |
How to read this card
- This is the first minute after launch with no action at all: what the program does on its own. Normal use may involve more requests.
- A “built-in SDK” means the library’s code was found. It does not prove data transfer, and an address in the code is not a request.
- The review was made automatically using a single method. You can check any program yourself here.