Most static findings are false positives from Markdown fences, inline code formatting, React examples, and documentation links. The remaining confirmed risks are user-invoked install commands that fetch external component or skill content, so users should review remote sources before running them.
1
Files scanned
141
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Lines 14-17 contain a bash quick-start example that runs npx and fetches a remote shadcn registry URL. This is user-invoked, but it still introduces external command and supply-chain risk.
The URL is passed to npx shadcn as a remote component registry source. This network dependency is expected, but users should review fetched code before installation.
Most static findings are false positives from Markdown fences, inline code formatting, React examples, and documentation links. The remaining confirmed risks are user-invoked install commands that fetch external component or skill content, so users should review remote sources before running them.
1
Files scanned
141
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Lines 14-17 contain a bash quick-start example that runs npx and fetches a remote shadcn registry URL. This is user-invoked, but it still introduces external command and supply-chain risk.
The URL is passed to npx shadcn as a remote component registry source. This network dependency is expected, but users should review fetched code before installation.
Most static external-command findings are Markdown fence false positives around TSX examples and role names. Two command blocks are real risks because they instruct users to run npx installers that fetch remote content, and one remote image plus one installer URL create low network exposure. No prompt injection or hidden data-exfiltration instructions were found.
1
Files scanned
141
Lines analyzed
6
Review items
0
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The range contains an npx shadcn@latest install command that downloads a registry entry from ui.inference.sh. This is a real supply-chain and network execution risk if an agent or user runs it.
This is a remote image URL; rendering the documentation can contact cloud.inference.sh and expose viewer metadata. It does not execute code, so the risk is low.
The URL is consumed by npx shadcn add to retrieve remote component metadata. This creates a real network and supply-chain dependency on mutable external content.
Most static external-command findings are Markdown fence false positives around TSX examples and role names. Two command blocks are real risks because they instruct users to run npx installers that fetch remote content, and one remote image plus one installer URL create low network exposure. No prompt injection or hidden data-exfiltration instructions were found.
1
Files scanned
141
Lines analyzed
6
Review items
0
False positives ignored
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The range contains an npx shadcn@latest install command that downloads a registry entry from ui.inference.sh. This is a real supply-chain and network execution risk if an agent or user runs it.
This is a remote image URL; rendering the documentation can contact cloud.inference.sh and expose viewer metadata. It does not execute code, so the risk is low.
The URL is consumed by npx shadcn add to retrieve remote component metadata. This creates a real network and supply-chain dependency on mutable external content.
Static analysis reported shell-like patterns, hardcoded URLs, and weak cryptography indicators. The weak cryptography indicators are false positives, while the documented npx commands and remote component registry URL create a real supply chain risk that users should review before running.
1
Files scanned
141
Lines analyzed
5
Review items
1
False positives ignored
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The quick start instructs users to run npx shadcn@latest against a remote component registry URL. This is legitimate for a UI component skill, but it executes package tooling and downloads remote content, so users must trust the upstream registry and package.
The command is shown directly in a bash block and references a remote registry URL. It appears intentional and relevant, but it still creates supply chain exposure if executed.
The related skills section documents npx skills add commands for additional community skills. These commands are not automatically executed, but they expand the trust boundary if users copy them.
The commands are explicit installation examples in documentation. There is no evidence of hidden execution, so the risk is user-driven rather than malicious.
The skill includes links to ui.inference.sh, cloud.inference.sh, and inference.sh documentation. These are normal marketplace references, with no evidence of credential collection or data exfiltration.
The URLs are visible Markdown links and an image reference. I found no script, beacon, or instruction to transmit local data to these endpoints.
Static false positives ignored (1)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Weak Cryptography Static Matches Are False Positives
The high-severity weak cryptography alerts do not correspond to hash, encryption, or signature code. The cited lines contain metadata, table text, and styling prose.
Manual review found no cryptographic API or weak algorithm use at the cited locations. The static pattern appears to match incidental text.
Static analyzer flagged 28 patterns that are all false positives. Markdown code block delimiters (```) were incorrectly detected as shell backtick execution. URLs are documentation links, not runtime network calls. No cryptographic code exists. This is a legitimate React UI component library documentation file with no security concerns.
1
Files scanned
141
Lines analyzed
2
Review items
2
False positives ignored
Static false positives ignored (2)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
Static analyzer detected 'Ruby/shell backtick execution' but these are Markdown code fence delimiters (```bash, ```tsx) used for documentation, not shell execution backticks. No command injection risk exists.
Hardcoded URLs detected are documentation and CDN links in markdown content (ui.inference.sh, inference.sh). These are reference links for users, not runtime network requests made by code.