alexgreensh/repo-forensics / skills/repo-forensics
repo-forensics
FlaggedSecurity forensics for git repos, AI skills, and MCP servers. Audits dependencies, detects prompt injection, credential theft, runtime dynamism, manifest drift, known CVEs, CISA KEV (actively exploited) vulns, and 2026 attack patterns. Not for fixing vulnerabilities or pentesting.
scripts/dast_sandbox.sb
View on GitHub(version 1)
;; Unknown capabilities stay denied. Explicit runtime reads let interpreters
;; and shared libraries load without granting host-wide file or IPC access.
(deny default)
(allow process-exec)
(allow process-fork)
(allow sysctl-read)
(allow file-read-metadata)
;; dyld opens the root directory while starting an executable.
(allow file-read-data (literal "/"))
(allow file-read* (subpath "/bin") (subpath "/sbin")
(subpath "/usr") (subpath "/System")
(subpath "/opt/homebrew")
(subpath "/Library/Frameworks/Python.framework")
(literal "/dev/null") (literal "/dev/urandom"))
;; Deny all network access — prevents data exfiltration
(deny network*)
;; Allow reads on the specific hook script being tested, otherwise
;; bash cannot open it and the scanner silently fails. HOOK_PATH and HOOK_DIR
;; are passed via `sandbox-exec -D` parameters.
;;
;; Why both HOOK_PATH (literal) AND HOOK_DIR (subpath)?
;; - literal HOOK_PATH: minimum needed so bash can load the hook itself.
;; - subpath HOOK_DIR: real hooks commonly `source "$(dirname "$0")/lib.sh"`
;; or read .claude/settings.json for config. Limiting to `literal` alone
;; would silently break any realistic multi-file hook setup.
;; This intentionally widens reads to the hook's containing directory only;
;; reads of unrelated /Users paths (credentials, shell rc files) stay denied.
(allow file-read* (literal (param "HOOK_PATH")))
(allow file-read* (subpath (param "HOOK_DIR")))
;; Hook code may run, but it must not modify the host filesystem.
(deny file-write*)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |