T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Third-Party Packages Are Installed and Executed
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This frontend debugging skill is coherent, but it needs review because it can inspect and retain sensitive browser activity and runs unpinned packages through the package registry.
Install only if you are comfortable giving the Harness-FE daemon access to sensitive frontend debugging telemetry. Prefer using it on local or test data, pin package versions, avoid production secrets in recorded sessions, clear ~/.harness/ when done, and ask the agent before it inspects recordings, cookies/storage, full network bodies, visitor timelines, or attachments.
SKILL.md:30Unpinned Third-Party Packages Are Installed and Executed
SKILL.md:281Frontend Recordings May Retain Unmasked Sensitive Form Data
The invocation language is broad enough that the skill may activate for generic frontend questions, not just explicit debugging tasks requiring this powerful telemetry bridge. That increases the chance the agent will unnecessarily reach for tools that can inspect live DOM, network, storage, visitor journeys, and recordings, expanding exposure of sensitive data beyond the minimum needed for the user's request.
The skill advertises capabilities to inspect network traffic, rrweb recordings, storage mutations, and visitor identity/journey data before presenting a prominent upfront privacy warning or consent gate. In context, these tools can reveal tokens, personal data, browsing behavior, and cross-tab/session activity, so omission of an early warning makes inadvertent over-collection or inappropriate inspection more likely.
The skill instructs use of npx @harness-fe/mcp-server without pinning an exact version, which allows whatever package version is current at execution time to be fetched and run. Because this is an MCP server with access to browser state, recordings, storage, network traffic, and page evaluation, a compromised or malicious upstream release could execute with broad debugging visibility and tool-mediated access.
No suspicious patterns detected.