Caveat verdict

rtk-integration

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Setup guide for the rtk CLI token-compression tool with transparent install instructions from a named GitHub repo; curl-pipe-to-sh is documented and expected for this type of CLI install, not a covert action.

⚠ 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.

13
security
60
transparency
70
maintenance

Permission integrity

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

network_out

Performs file operations but does not declare file-accessing binaries

file_read+write

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (2)

Pattern match critical

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

SKILL.md · code · curl -fsSL https://raw.githubusercontent.com/rtk-ai/rtk/refs/heads/master/instal

Pattern match critical

Pipe to sh — executes piped content as shell commands

SKILL.md · code · | sh

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B/F). 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_outfile_writepackage_installdata_encoding

Is this flag fair?

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