socket-inspect

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The skill embeds a literal API token in an example command (a secret-looking string), which would require the LLM to reproduce that secret verbatim and thus constitutes insecure credential handling.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (medium risk: 0.30). In SKILL.md, the runtime workflow ingests outsider-authored free text via WebFetch scraping of the socket.dev package page URL (constructed from user-supplied {name}/{ecosystem} in Step 2), and also via GitHub API data for maintenance health (Step 3d) which may include issue/PR text from third parties.

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). Line 43 contains a high-entropy, literal API token value used to authenticate the Socket CLI demo ("sktsec_t_..."). This is not a placeholder (it is a concrete token string) and therefore qualifies as a credential present in the documentation. Although the doc describes it as a "public demo token" with limited permissions, it is still an active-looking secret embedded in the file and should be treated as a leaked credential or redacted.