quiet_clock

Bottom line

quiet_clock is a five-line Qt Quick view: a black Rectangle, a centred Text, and a one-second Timer that writes Qt.formatDateTime(new Date(), "hh:mm:ss") into the label (Main.qml:1-5). The module has no message or IPC handlers, no file paths, no network endpoints, no crypto or key material, no authentication or capability checks, no QML-to-native calls, and no build, install, or CI scripts. The only runtime inputs are the host-supplied system clock and Qt itself, both outside the module's control. On this source I found no Critical, High, or Medium issue and no exploitable input-to-sink path.

The weak points are assurance and packaging, not exploitability. The README asserts a security property ("No network, no storage, nothing else") that nothing in the repo enforces or verifies (README.md:2); there is no published .lgx in /run/lgx, no checksum or signature, and no packaging recipe tying the source commit to what a user installs (metadata.json:1-2); the timer runs unconditionally even if the host keeps a hidden view alive (Main.qml:4-5); and the supplied "clean" static reports carry almost no signal because the semgrep invocation used zero rules. These are all marked [read] and rated Low.

Dynamic verification failed for environmental reasons. Basecamp's AppRun aborted twice before any module could be opened, with Failed to load the main UI plugin ... main_ui.so: The shared library was not found. No .lgx was published to install, and the locally synthesised test package was never installed because Basecamp never stayed up. Consequently the README's runtime claim remains unverified by execution, not refuted: the code is consistent with it, but this review did not observe it in Basecamp.

The absence of findings above Low is a statement about a very small surface, not a certification. The module should be treated as low-risk but not as independently verified until it can be built and exercised in a working Basecamp.

What the module did

Nothing flagged: no bait read or sent, no unexpected traffic.

Findings (0)

See report.md.

Screens and recording

What is solid

• Main.qml:1-5 imports only QtQuick; there is no eval, Function, dynamic import, XMLHttpRequest, fetch, FileIO, Storage, Network, Process, WebSocket, or Qt Labs module. There is no string concatenation into a path, SQL statement, HTML/text markup, or command.
• The only data flow is new Date() → Qt.formatDateTime(..., "hh:mm:ss") → Text.text. The format string is a constant, the colours are constants, and no value from outside the process reaches a sink.
• The module has no native code, no plugin binaries, no shared-library loading, no CMakeLists.txt, no package.json, and no install hooks; nothing in the repo fetches or executes during a build.
• metadata.json is internally consistent: name is quiet_clock, type is ui_qml, and the declared view (Main.qml) exists at the repository root. No dependencies are declared.
• The git repository is minimal and clean: 5 objects, one commit, no alternate branches, no stash, and no unreachable objects found by git fsck. There is no hidden payload in the history.
• gitleaks reports no secrets and OSV reports no vulnerable dependencies; this is consistent with the absence of credentials and dependency manifests, though it is weak evidence by itself.
• No bait file under /root was opened by this review, and the sandbox's dns.log is empty. The retained strace.log shows only the review agent's own processes talking to the model gateway, not the module.

What was not tested

• Basecamp execution: desk start twice reached Xvfb and the recorder, but LogosBasecamp aborted with a missing main_ui.so; the module was never opened, so no screen, icon, timer update, or runtime network/file activity was observed.
• desk install: not run. There is no publisher .lgx; the locally synthesised /run/lgx/quiet_clock-1.0.0.lgx was never installed into a working Basecamp.
• Screenshots and the session video: no PNGs were produced, and only a 32 KB partial session.mp4 exists from the failed startup.
• Runtime syscall tracing: strace is blocked by ptrace policy; the harness could not load QtQuick because the system QML runtime tree is absent. Therefore "no network, no storage" is supported by source inspection only, not execution.
• No fuzzing or hostile-input testing: the module takes no user input, messages, paths, or files; the only external input is the system clock.
• Not tested: timezone/locale variation, system clock jumps or attacker-controlled TZ, suspend/resume behaviour, multiple simultaneous instances, and host policy for destroying hidden plugin views.
• No sanitizer run was applicable to pure QML. No ASan/UBSan build exists because there is no compiled code.
• The publisher's build, catalogue metadata, signing, and update path were not available to verify.

Suggested order

• Publish a reproducible, signed .lgx with a checksum and a manifest that records the source commit, Qt/Basecamp minimum version, and permissions (FR-2). This is the prerequisite for any later runtime review.
• Replace the README's absolute security claim with a precise scope statement, and enforce it with an import deny-list test and a real semgrep ruleset in CI (FR-1, FR-4).
• Gate the timer on visibility/application state to avoid background wakeups (FR-3).
• Once Basecamp starts successfully in the sandbox, re-run this review dynamically: install the published package, open the module, capture the clock and a minute of updates, and trace the module process for file/network syscalls.

--- Triage, not approval — this never certifies a module as safe. The sandbox is a container; its kernel is the host's and could be detected.

What the reviewer ran

• find . -type f, ls -la, git log --oneline, git branch -a, git stash list, git count-objects -v, git fsck --lost-found — repository contains exactly Main.qml, README.md, metadata.json; one commit 002ac71 init; 5 loose git objects, no extra branches, refs, stashes, or unreachable blobs. [run]
• cat -n Main.qml, cat README.md, cat metadata.json — source and metadata read in full; contents match the five-line listing in section 1. [run]
• cat /run/checks/gitleaks.json, osv.json, semgrep.json — gitleaks [], OSV {"results":[]} with no dependency manifest present, semgrep "results":[] but also "rules":[], so the semgrep report is vacuous rather than a negative scan. [run]
• cat /run/behaviour/{bait,disguise,sandbox-check}.json, dns.log, and inspection of strace.log — dns.log is empty; strace.log records the review agent's own execve calls (pi, node, bash, grep, etc.) to the model gateway, not module activity. Bait file contents under /root were never opened; only the sandbox's own metadata listing was read. [run]
• qmllint -I /usr/lib/x86_64-linux-gnu/qt6/qml Main.qml — fails with "Failed to import QtQuick" and cascading unresolved-type warnings because the system installation has no Qt Quick QML runtime module. This is an environment limitation, so it neither validates nor invalidates the file. Exit 255. [run]
• Built a minimal QQmlApplicationEngine harness (g++ ... $(pkg-config --cflags --libs Qt6Qml Qt6Quick Qt6Gui)) — compiled successfully, but could not run: the system lacks the QtQuick runtime import tree. [run]
• strace -f ... /tmp/harness Main.qml — blocked by the sandbox: ptrace(PTRACE_TRACEME, ...): Operation not permitted. No runtime syscall trace of the QML could be produced. [run]
• Synthesised a test package: tar czf /run/lgx/quiet_clock-1.0.0.lgx containing manifest.json and variants/linux-amd64/Main.qml; SHA-256 b0102a2b7520a2535677bfd6f9a4922ba2896d53224b118643c2f1a709ed6e11. This is a reviewer artefact, not the publisher's package. [run]
• desk start (twice, with Xvfb and the recorder running) — Xvfb :99 came up and the recorder started, but LogosBasecamp aborted. /run/media/basecamp.log ends with MainUIBackend created and Failed to load the main UI plugin from .../plugins/main_ui/main_ui.so: The shared library was not found; the AppRun child was reported Aborted (core dumped). The module was never opened. [run]
• desk read / desk log during the failed starts — desk read failed with Cannot open display :99 while Xvfb was down; after a clean Xvfb start Basecamp had already aborted, so there was no window to read. [run]
• No probes were executed. /run/probes does not exist; the module exposes no parser, message, path, or user-input surface to drive one. No desk install was possible because no publisher .lgx exists and Basecamp did not stay up.
• Screenshots: none. /run/media contains only basecamp.log and a partial session.mp4 (32 KB) recorded while the aborted startup produced no usable Basecamp screen; no PNG evidence exists because desk shot was never reached. [run]

Usage and cost

Logos Storage

This review, every file of it, as one archive: zDvZRwzm9LWL88C6V7GVDBMP1CA6pkcgmPJR65Pzh7UhSQrJ4Xj5 on logos.test (665,389 bytes, sha256 838de4188a37b89e…). Any Logos Storage node on that network can fetch it by its CID while one holds it: the review host's node does; nothing pays for more.

Evidence

• report.md: the reviewer's full writeup · report.json
• session.log: the reviewer's session · gateway.jsonl: every model request and reply
• behaviour/: strace, DNS, the proxies' request logs, bait, the sandbox's self-check · checks/: gitleaks, osv-scanner, semgrep · media/
• chain.txt: the hash-chain root over every file of the run · live.txt: the running transcript