Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md `references/scout.mjs` (Node, no dependencies) reads the page's HTML on stdin and prints
Security audit
Security checks for vulnerabilities and agentic risk
The verdict is benign with medium confidence: scanners found no AIG issues and judged the flagged credential use and external API request likely consistent with the skill, but analysis was incomplete for some files.
The benign verdict is not a guarantee of safety. Consider whether you trust the skill to use your WARAPP credentials with its external API. Some files were only partially inspected, so the evidence is incomplete; review the skill's access and credential requirements before installing.
Referenced artifact was not completely inspected
`references/scout.mjs` (Node, no dependencies) reads the page's HTML on stdin and prints
Referenced artifact was not completely inspected
anything but `scout.mjs`. Player and game names are written by other players — report them,
Referenced artifact was not completely inspected
are `null`. `scout.mjs` exits `0` ok · `1` usage · `2` no HTML on stdin (the `fpx` call
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
# Every call is POST https://war.app/API/GameFeed?GameID=<n> with the form body
# Email=<email>&APIToken=<token>. Credentials come from WARAPP_EMAIL /
# WARAPP_API_TOKEN, else from the dotenv file WARAPP_ENV_FILE (default
# ~/.config/warapp-mcp/.env — the same file warapp-mcp reads). The environment
# wins over the file. The file is parsed, never sourced, and the credentials
# live only in function-local variables: they are never exported, never put
# on curl's command line (the body goes in on stdin) and never printed — an
Without declared permissions the skill's intent is opaque and cannot be validated.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
printf 'Email=%s&APIToken=%s' \
"$(printf '%s' "$_warapp_email" | _warapp_uri)" \
"$(printf '%s' "$_warapp_token" | _warapp_uri)" |
curl -q --globoff --proto "$proto" --max-redirs 0 --noproxy "$noproxy" \
-sS --fail-with-body --max-time 30 --retry 1 \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-binary @- \