rust-security-boundary-review

Review Rust code for auth, secret, input-sink, and browser credential boundary failures.

2|Updated May 6, 2026
One-click install
npx skills add https://github.com/bpcakes/jig-skills --skill rust-security-boundary-review-bpcakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-security-boundary-review
Source: https://github.com/bpcakes/jig-skills/tree/main/plugins/jig-rust/skills/rust-security-boundary-review
Command: npx skills add https://github.com/bpcakes/jig-skills --skill rust-security-boundary-review-bpcakes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Security findings in Rust web services are easy to bury under architecture, error-handling, or test-review noise, and generic audits waste effort on out-of-scope concerns. This Skill performs a narrow, evidence-based review of seven specific security boundaries so concrete vulnerabilities surface with file/line proof instead of speculative warnings. ## Core Features & Use Cases - Boundary-scoped review: Covers secret exposure, authentication/authorization layering, untrusted-input sinks (SQL, paths, redirects, headers, shell), CORS/cookies, token comparison, rate limiting, and error-response leakage. - Evidence-first methodology: Requires tracing attacker-controlled sources to sensitive sinks before reporting, with severity assigned by impact and reachability, plus a separate Needs verification section for unresolved facts. - Optional scanner and references: Ships a ripgrep-based lead-generation script and boundary-specific reference checklists for secrets, input sinks, and browser/token/diagnostic concerns. - Use Case: Before merging a pull request that adds a new authenticated endpoint, run this review on the diff to confirm authorization is enforced at the service layer, tokens are compared in constant time, and error responses do not leak internals. ## Quick Start Ask the agent to review the current working changes with the rust-security-boundary-review skill and report findings with file locations without editing code.

Frequently Asked Questions about rust-security-boundary-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review Rust code for security vulnerabilities in a pull request?

Run this review against the PR diff using git diff to scope the target, then build a boundary map of entry points, untrusted inputs, identity context, and sensitive sinks. Findings are reported only after tracing concrete dataflow with file and line evidence.

What security issues does a Rust security boundary review check?

It checks seven boundaries: secret exposure through logging or serialization, auth/authz at the wrong layer, user input controlling SQL, paths, redirects, headers, or shell commands, permissive CORS and weak cookies, unsafe token comparison or tokens in URLs, missing rate limiting, and error responses leaking internals.

Does this review cover dependency CVEs or unsafe Rust code?

No. Dependency CVEs, supply-chain audits, memory safety, unsafe blocks, TLS configuration, and general input validation are explicitly out of scope. The review stays focused on the seven defined security boundaries unless the user requests a broader audit.

How are severity levels assigned to Rust security findings?

Severity is based on impact and reachability: Critical for auth bypass or command injection, High for SQL injection or plaintext secret exposure, Medium for bounded boundary failures, and Low for limited-impact defects. Hardening suggestions are kept separate from confirmed findings.

What tools are required to run the security boundary scan script?

The optional helper script requires ripgrep (rg) and a bash environment. It generates a lead list of pattern matches across routes, secrets, sinks, CORS, cookies, tokens, and rate limiting, but every match must be manually verified before becoming a finding.