Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md ./scripts/mean-marketer.js setup # prompts, input hidden
Security audit
Security checks for vulnerabilities and agentic risk
ClawScan marks this skill benign because it found no definite harmful behavior, but confidence is medium and part of the referenced script could not be fully inspected.
The verdict is benign, but the evidence is incomplete: only half of the components were fully scanned, and the script analysis was partial. Consider waiting for a complete review before installing if you need confidence about the script’s behavior.
Referenced artifact was not completely inspected
./scripts/mean-marketer.js setup # prompts, input hidden
Referenced artifact was not completely inspected
printf %s "$TOKEN" | ./scripts/mean-marketer.js setup # or pipe it
Referenced artifact was not completely inspected
./scripts/mean-marketer.js config # show current config
Referenced artifact was not completely inspected
./scripts/mean-marketer.js config --min-score 60 # only surface leads scoring >= 60 (50-100)
Referenced artifact was not completely inspected
./scripts/mean-marketer.js config --enabled false # pause the whole loop
Referenced artifact was not completely inspected
./scripts/mean-marketer.js config --profanity false # keep it savage but swear-free
Referenced artifact was not completely inspected
./scripts/mean-marketer.js config --website <websiteId> # only nag about one monitored site
Referenced artifact was not completely inspected
./scripts/mean-marketer.js notify
Referenced artifact was not completely inspected
*/5 * * * * cd /path/to/redreplier-mean-marketer && node scripts/mean-marketer.js notify
Referenced artifact was not completely inspected
To test without scheduling anything, just run it once: `./scripts/mean-marketer.js notify`
Referenced artifact was not completely inspected
./scripts/mean-marketer.js triage --id <opportunity_id> --status APPROVED # or REJECTED
Without declared permissions the skill's intent is opaque and cannot be validated.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
The token never appears in a command-line argument. `setup` reads it from a hidden prompt
or from stdin, and refuses a `--key` flag outright. Keep it out of your crontab too: the
cron examples below rely on the stored config file rather than an inline variable, so the
secret stays in one `600` file instead of being copied into `crontab -l` output, process
listings and backups.
To rotate or revoke, delete `~/.config/redreplier/config.json` and generate a new token at