cc.roboparts/roboparts v1.1.1

Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Tool and prompt definitions stay fixed during a session — they don't change after a few calls, which is how runtime-gated rug-pulls slip past one-time review.

No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Untrusted tool input reaching a shell yields remote code execution.

Fix: Never pass tool arguments to a shell; use argv arrays with shell disabled.

Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

Fix: Resolve to a canonical path and verify containment; reject ../ and symlinks.

Fetching tool-supplied URLs can pivot into internal networks and metadata services.

Fix: Allow-list destinations; reject arbitrary/loopback/link-local URLs.

Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

Fix: Upgrade the flagged dependencies past their fixed versions.

A SECURITY.md gives a private path to report vulnerabilities.

Fix: Add SECURITY.md with a disclosure contact and process.

A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

Fix: Adoption grows naturally with real-world use; this never gates the score.

eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

pickle/yaml.load/etc. on untrusted data can execute code.

Hardcoded keys/tokens in published source are live credentials an attacker can use.

Reading secrets from env/secret stores avoids hardcoding them.

A lockfile makes installs reproducible and resistant to silent dependency swaps.

Unmaintained servers don't receive security fixes.

Archived repositories will never be patched.

A clear license is required for legal enterprise use.

The client's token is never forwarded to downstream APIs — the server obtains its own, correctly-scoped credential instead.

Fix: Accept only tokens issued for this server; obtain a separate downstream token via OAuth token exchange or client credentials.

A container/sandbox image limits blast radius; a server that runs natively has full host access.

Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

Plaintext HTTP exposes traffic and bearer tokens to interception.

OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.