Tidbyt Status Display

• Outcome: Pass
• Latest audit: May 28, 2026, 11:13 AM
• Version:
  1.0.0

Overview

This skill does what it claims: it runs a local status API for a Tidbyt display, but users should keep that API on a trusted network.

Install only if you want your agent status visible to a Tidbyt or dashboard. Run it on a trusted LAN, avoid exposing port 8765 to the internet, restrict firewall access where possible, and use the optional background/systemd mode only if you want the API running continuously.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (3)

Missing User Warnings

Medium

• Confidence: 87% confidence
• Finding: The README instructs users to configure the display to fetch status data from a local API over plain HTTP, which can expose agent activity information to anyone on the same network and allows tampering if the network is untrusted. While this is likely intended for simple local-network use, the lack of any warning, authentication, or transport protection makes accidental data exposure and spoofed status responses more likely.

Missing User Warnings

Medium

• Confidence: 93% confidence
• Finding: The documentation instructs users to expose a status API on the local network and open a firewall port, but it does not warn that the endpoint reveals agent activity metadata such as status, timestamps, and recent activity. Even if the data seems low sensitivity, exposing operational telemetry without authentication or privacy guidance can leak behavior patterns to anyone on the network.

Missing User Warnings

Medium

• Confidence: 94% confidence
• Finding: The server binds to 0.0.0.0 and exposes detailed agent activity, task counts, timestamps, and recent activity strings to any network client without authentication or access controls. Even though this appears intended for Tidbyt integration, it creates an information disclosure issue because anyone who can reach the port can monitor operator presence and agent workload, and the wildcard CORS header further broadens access from browser-based clients.

VirusTotal

66/66 vendors flagged this skill as clean.