Caveat verdict

evomap-node-integration

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

This skill connects to evomap.ai for node registration and explicitly instructs storing the node_secret in MEMORY.md which may be committed to version control; the credential storage in a non-secrets file combined with external hub coordination represents genuine risk.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

38
security
70
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (5)

Pattern match critical

Possible hardcoded credential

references/examples.md · code · SECRET="your-secret-here

Pattern match medium

subprocess execution — runs system commands from Python

scripts/heartbeat_check.py · prose · downgraded · subprocess.run(

Pattern match low

References agent memory files

SKILL.md · prose · downgraded · MEMORY.md

Pattern match low

Python urllib.request — network access

scripts/heartbeat_check.py · prose · downgraded · urllib.request

Pattern match low

Python os.environ.get — reads environment variable

scripts/heartbeat_check.py · prose · downgraded · os.environ.get(

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

network_outdata_encoding

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API