clawsouls

clawhub:clawsouls

View source
A
92/100

First Seen

Feb 18, 2026

Last Scanned

Feb 22, 2026

Findings

3

Score

92/100

MEDIUM 1
LOW 2

Findings (3)

MEDIUM
Conditional download and install
L20

Detects patterns that check for tool existence and install if missing

If not installed, install
FIX

Replace conditional download-and-install logic with explicit dependency declarations in a manifest file (package.json, requirements.txt). Verify checksums for any runtime downloads.

FP?

Likely FP if the conditional install is documentation showing standard prerequisite checks (e.g., checking if a tool is installed before installing it).

LOW
Global package installation
L23

Detects global installation of packages which affects the host system

npm install -g c
FIX

Replace npm install -g with a local install (npm install --save-dev) or use npx with a pinned version. Global installs modify the system and risk supply chain attacks.

FP?

Likely FP if the global install is for a well-known CLI tool (e.g., typescript, eslint) in setup documentation, though the supply chain risk remains real.

LOW
Runtime URL controlling behavior
L139

Detects URLs fetched at runtime that control or influence agent behavior without pinning

get API token: Sign in at https:// + prompt
FIX

Avoid loading configuration or behavior-controlling content from runtime URLs. Bundle required configurations locally or pin remote config to versioned, integrity-verified endpoints.

FP?

Likely FP if the URL in the match is a documentation link or example URL (e.g., example.com) rather than an actual runtime-fetched configuration endpoint.