Is russellading/qBittorrent safe?
Yes. russellading/qBittorrent is safe to install. Oathe's behavioral security audit gave the qBittorrent skill by russellading a trust score of 93/100 with 5 findings, none critical or high.
https://github.com/russellading/qBittorrent
Is russellading/qBittorrent safe to install?
This repository is a fork of the legitimate qBittorrent open-source project with a completely empty SKILL.md, making it non-functional as an LLM agent skill. No prompt injection, no suspicious network exfiltration, no git hooks, no auto-executing malicious code, and all canary honeypot files remain intact. The only minor observations are pre-clone canary file reads attributable to the audit framework's baseline phase and a non-registry npm tarball dependency that is never auto-executed.
What security issues were found in russellading/qBittorrent?
Category Scores
Findings (5)
INFO SKILL.md is completely empty 0 ▶
The SKILL.md file contains no content whatsoever. This means the repository provides no skill functionality — no instructions are injected into the agent's system prompt. While this eliminates prompt injection risk entirely, it also means the skill is non-functional.
Evidence: SKILL.md content: empty (zero bytes of instruction content)
LOW Canary files read-accessed before clone (audit infrastructure artifact) 12 ▶
Six canary files (.env, .ssh/id_rsa, .aws/credentials, .npmrc, .docker/config.json, .config/gcloud/application_default_credentials.json) were opened with read-only access (CLOSE_NOWRITE) at timestamp 1794413840 (16:17:20), approximately 6 seconds before the git clone began at 1794413846 (16:17:26). The timing and access pattern strongly indicate these reads are from the audit framework's baseline/canary establishment phase, not from repository code. All canary files remain intact per the integrity check.
Evidence: inotify: 16:17:20 OPEN /home/oc-exec/.env; CLOSE_NOWRITE. Git clone EXECVE at audit(1794413846.187): git clone https://github.com/russellading/qBittorrent
LOW GitHub tarball dependency in package.json 8 ▶
The WebUI package.json includes eslint-plugin-qbt-webui fetched via a GitHub tarball URL rather than the npm registry. If a developer runs npm install, this dependency is fetched from an external non-registry source. Not auto-executed on clone.
Evidence: package.json: "eslint-plugin-qbt-webui": "https://github.com/Chocobo1/eslint-plugin-qbt-webui/tarball/v1"
INFO Pre-commit hooks reference external repositories 5 ▶
The .pre-commit-config.yaml configures hooks from github.com/pre-commit/pre-commit-hooks, codespell-project/codespell, and crate-ci/typos. These are not auto-executed on git clone and only run if pre-commit is installed and activated. The referenced repos are well-known, legitimate projects.
Evidence: .pre-commit-config.yaml: repos include https://github.com/pre-commit/pre-commit-hooks.git rev: v6.0.0, etc.
INFO Fork of legitimate qBittorrent project with no SKILL.md 0 ▶
This is a fork of the official qBittorrent open-source BitTorrent client. As a skill, it is completely non-functional since SKILL.md is empty. The large C++ codebase provides no agent instructions and poses no behavioral risk in the current state.
Evidence: Repository structure matches upstream qBittorrent (src/gui/, src/base/, src/webui/, CMakeLists.txt, AUTHORS, COPYING.GPLv3)
Should I install russellading/qBittorrent?
Oathe's verdict for russellading/qBittorrent is SAFE with a trust score of 93/100. Recommendation: Install.