codejury 1.3.0__tar.gz → 1.4.1__tar.gz

{codejury-1.3.0 → codejury-1.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codejury
-Version: 1.3.0
+Version: 1.4.1
 Summary: AI-assisted security review for code diffs and whole repositories.
 Author: AISecLabs
 License-Expression: MIT
@@ -84,8 +84,10 @@ codejury install-slash-command                  # Claude Code
 codejury install-slash-command --agent codex    # Codex
 ```
 
-`install-slash-command` copies `/codejury-review-repo` into the selected agent's command
-directory. Pass `--dir` to install it somewhere else.
+`install-slash-command` copies `/codejury-review` into the selected agent's command
+directory. The one command dispatches by argument: a directory runs the Repo Review
+fan-out, a diff file or git range runs the coded Diff Review. Pass `--dir` to install it
+somewhere else.
 
 ## Configure a Model Backend
 
@@ -232,7 +234,7 @@ _pocs.md        PoC reconciliation, planned versus delivered
 Then run the interactive slash command in Claude Code or Codex:
 
 ```text
-/codejury-review-repo /path/to/repo
+/codejury-review /path/to/repo
 ```
 
 The agent maps the attack surface, fills the authorization model, runs one focused
@@ -294,7 +296,7 @@ Current guide coverage in the web domain includes:
 - Python: Django, Flask, FastAPI, Celery
 - Go: Gin, Echo
 - JavaScript and TypeScript: Express, NestJS
-- Protocols: OAuth and OIDC
+- Protocols: OAuth, OIDC, and GraphQL
 
 The evm domain ships a Solidity guide and the smart contract vulnerability classes above.
 Unguided stacks still work, but the agent relies more on general methodology and model

{codejury-1.3.0 → codejury-1.4.1}/README.md

@@ -42,8 +42,10 @@ codejury install-slash-command                  # Claude Code
 codejury install-slash-command --agent codex    # Codex
 ```
 
-`install-slash-command` copies `/codejury-review-repo` into the selected agent's command
-directory. Pass `--dir` to install it somewhere else.
+`install-slash-command` copies `/codejury-review` into the selected agent's command
+directory. The one command dispatches by argument: a directory runs the Repo Review
+fan-out, a diff file or git range runs the coded Diff Review. Pass `--dir` to install it
+somewhere else.
 
 ## Configure a Model Backend
 
@@ -190,7 +192,7 @@ _pocs.md        PoC reconciliation, planned versus delivered
 Then run the interactive slash command in Claude Code or Codex:
 
 ```text
-/codejury-review-repo /path/to/repo
+/codejury-review /path/to/repo
 ```
 
 The agent maps the attack surface, fills the authorization model, runs one focused
@@ -252,7 +254,7 @@ Current guide coverage in the web domain includes:
 - Python: Django, Flask, FastAPI, Celery
 - Go: Gin, Echo
 - JavaScript and TypeScript: Express, NestJS
-- Protocols: OAuth and OIDC
+- Protocols: OAuth, OIDC, and GraphQL
 
 The evm domain ships a Solidity guide and the smart contract vulnerability classes above.
 Unguided stacks still work, but the agent relies more on general methodology and model

{codejury-1.3.0 → codejury-1.4.1}/codejury/cli.py

@@ -366,8 +366,10 @@ def main(argv: list[str] | None = None) -> int:
         _add_role_backend_args(roles, role)
 
     tuning = repo.add_argument_group("run tuning (advanced)", "only affect --run, sane defaults otherwise")
-    tuning.add_argument("--max-passes", type=int, default=24, dest="max_passes",
-                        help="cap on diverse passes before stopping")
+    tuning.add_argument("--max-passes", type=int, default=None, dest="max_passes",
+                        help="cap on diverse passes before stopping, default scales to the domain: "
+                             "(min-lens-shots + 1) * number of lenses, so every lens meets its shot "
+                             "floor with a cycle of headroom for convergence")
     tuning.add_argument("--converge-after", type=int, default=2, dest="converge_after",
                         help="stop once this many consecutive passes add no new finding")
     tuning.add_argument("--min-lens-shots", type=int, default=2, dest="min_lens_shots",
@@ -382,12 +384,12 @@ def main(argv: list[str] | None = None) -> int:
     _add_domain_arg(repo)
 
     inst = sub.add_parser("install-slash-command",
-                          help="install the /codejury-review-repo slash command for an agent")
+                          help="install the /codejury-review slash command for an agent")
     inst.add_argument("--agent", choices=("claude", "codex"), default="claude",
                       help="which agent's command directory to install into")
     inst.add_argument("--dir", default=None, help="explicit target directory, overrides --agent")
     inst.add_argument("--force", action="store_true",
-                      help="overwrite an existing codejury-review-repo.md at the destination")
+                      help="overwrite an existing codejury-review.md at the destination")
     inst.add_argument("--domain", default="web", metavar="DOMAIN",
                       help="which domain's slash command to install, one of: " + ", ".join(available_domains()))
 
@@ -411,6 +413,49 @@ def _diff_provider(args, spec, kind: str):
     return _role_provider(args, spec)
 
 
+def build_diff_providers(args):
+    """Resolve the diff seats into providers exactly as `review diff` does, so a non-CLI caller
+    such as the eval runs a case through the same wiring a user gets. Returns the base provider
+    and model the audit needs plus the per-role finder, challenger, and judge providers and
+    models, the role fields None in standard mode. The single source the CLI and the eval share,
+    so the probe cannot drift from the product on which model or seat reviews a diff."""
+    base = _base_spec(args)
+    if args.mode == "adversarial":
+        roles = {r: _role_spec(args, r, base) for r in ("finder", "challenger", "judge")}
+        kinds = {r: _seat_backend(s, args.executor) for r, s in roles.items()}
+        agent_roles = [r for r, k in kinds.items() if k == "agent"]
+        _warn_roles_under_agent(args, agent_roles)
+        if args.executor == "auto":
+            _note_subscription_fallback(agent_roles)
+        fp = _diff_provider(args, roles["finder"], kinds["finder"])
+        cp = _diff_provider(args, roles["challenger"], kinds["challenger"])
+        jp = _diff_provider(args, roles["judge"], kinds["judge"])
+        return (fp, roles["finder"]["model"], fp, roles["finder"]["model"],
+                cp, roles["challenger"]["model"], jp, roles["judge"]["model"])
+    base_kind = _seat_backend(base, args.executor)
+    if args.executor == "auto" and base_kind == "agent":
+        _note_subscription_fallback(("audit",))
+    return (_diff_provider(args, base, base_kind), base["model"], None, None, None, None, None, None)
+
+
+def diff_args_from_env(mode: str, *, executor: str = "auto", rounds: int = 3):
+    """A diff args namespace from the environment defaults, the same values `review diff` reads
+    when no flag is passed, so `build_diff_providers` builds the user's real wiring. Lets the eval
+    drive the audit through the product path rather than a hardcoded provider."""
+    from types import SimpleNamespace
+    ns = dict(provider=DEFAULT_PROVIDER, model=DEFAULT_MODEL, api_key=DEFAULT_API_KEY,
+              api_base=DEFAULT_API_BASE, retries=DEFAULT_RETRIES, timeout=DEFAULT_TIMEOUT,
+              executor=executor, mode=mode, rounds=rounds)
+    for role in ROLES:
+        d = DEFAULT_ROLE_BACKENDS[role]
+        ns[f"{role}_provider"] = d["provider"]
+        ns[f"{role}_model"] = d["model"]
+        ns[f"{role}_api_key"] = d["api_key"]
+        ns[f"{role}_api_base"] = d["api_base"]
+        ns[f"{role}_wire_api"] = d["wire_api"]
+    return SimpleNamespace(**ns)
+
+
 def _dispatch(args, parser) -> int:
     scope = getattr(args, "scope", None)
     if args.command == "review" and scope == "diff":
@@ -424,29 +469,8 @@ def _dispatch(args, parser) -> int:
         else:
             diff = _read_diff(args)
             domain = resolve_domain(args.domain, _diff_paths(diff))
-            base = _base_spec(args)
-            if args.mode == "adversarial":
-                # each seat resolves on its own key, so a keyless Claude finder and judge ride the
-                # subscription while an OpenAI challenger uses its own key. The finder backs the base
-                # default audit_diff needs, the per-role providers below override it field by field
-                roles = {r: _role_spec(args, r, base) for r in ("finder", "challenger", "judge")}
-                kinds = {r: _seat_backend(s, args.executor) for r, s in roles.items()}
-                agent_roles = [r for r, k in kinds.items() if k == "agent"]
-                _warn_roles_under_agent(args, agent_roles)
-                if args.executor == "auto":
-                    _note_subscription_fallback(agent_roles)
-                finder_provider = _diff_provider(args, roles["finder"], kinds["finder"])
-                challenger_provider = _diff_provider(args, roles["challenger"], kinds["challenger"])
-                judge_provider = _diff_provider(args, roles["judge"], kinds["judge"])
-                finder_model = roles["finder"]["model"]
-                challenger_model = roles["challenger"]["model"]
-                judge_model = roles["judge"]["model"]
-                provider, model = finder_provider, roles["finder"]["model"]
-            else:
-                base_kind = _seat_backend(base, args.executor)
-                if args.executor == "auto" and base_kind == "agent":
-                    _note_subscription_fallback(("audit",))
-                provider, model = _diff_provider(args, base, base_kind), base["model"]
+            (provider, model, finder_provider, finder_model,
+             challenger_provider, challenger_model, judge_provider, judge_model) = build_diff_providers(args)
         kept, _, degraded = audit_diff(
             diff, provider=provider, model=model,
             mode=args.mode, max_rounds=args.rounds, filter_findings=not args.no_filter,
@@ -457,7 +481,7 @@ def _dispatch(args, parser) -> int:
         print(render(args.fmt, kept))
         if degraded:
             # the adversarial judge was unusable and the result fell back to the
-            # unjudged set, so this is a failed audit, not a clean pass, invariant 3
+            # unjudged set, so this is a failed audit, not a clean pass, invariant 4
             print("error: the adversarial audit degraded on an unusable judge reply, "
                   "the result is incomplete and not a clean pass", file=sys.stderr)
         return 1 if degraded or gate(kept, args.fail_on) else 0
@@ -518,13 +542,17 @@ def _dispatch(args, parser) -> int:
               f"PoC reconciliation in {fr.workspace}/_pocs.md")
         if fr.verify and fr.verify.errors:
             print(f"WARNING: {fr.verify.errors} verification calls failed. Re-run to resume.", file=sys.stderr)
-            return 1   # fail loud: an incomplete verification is not a clean finalize, invariant 3
+            return 1   # fail loud: an incomplete verification is not a clean finalize, invariant 4
         return 0
 
     if args.command == "review" and scope == "repo" and args.run:
         from codejury.review.repo.engine import run_repo_review
         from codejury.review.repo.verifier import ModelVerifier
         domain = resolve_domain(args.domain, _repo_file_names(args.directory))
+        # scale the pass cap to the domain, so the min-lens-shots floor is always meetable and the
+        # convergence early-stop can fire, with one lens cycle of headroom above the floor
+        if args.max_passes is None:
+            args.max_passes = (args.min_lens_shots + 1) * len(domain.lenses)
         _warn_secondary_env()
         base = _base_spec(args)
         finder = _role_spec(args, "finder", base)
@@ -600,7 +628,7 @@ def _dispatch(args, parser) -> int:
                   file=sys.stderr)
         print(f"Findings written to {res.scaffold.workspace}/findings/ and {res.scaffold.workspace}/findings.json")
         # fail loud: a partial run or a run still finding issues at the cap must not exit clean,
-        # invariant 3 and the stability red line, so a non-converged run is not reported as done
+        # invariant 4 and the stability red line, so a non-converged run is not reported as done
         return 1 if failures or not acc.converged else 0
 
     if args.command == "review" and scope == "repo":
@@ -633,7 +661,7 @@ def _dispatch(args, parser) -> int:
         print(
             "This command sets up the review, it does not find anything itself. Next, have an "
             f"interactive agent follow {res.workspace}/METHODOLOGY.md to run the review, or use the "
-            "/codejury-review-repo command in Claude Code or Codex. The agent proposes findings in "
+            "/codejury-review command in Claude Code or Codex. The agent proposes findings in "
             f"{res.workspace}/candidates/, finalize confirms them into {res.workspace}/findings/."
         )
         return 0
@@ -645,14 +673,14 @@ def _dispatch(args, parser) -> int:
             "codex": Path.home() / ".codex" / "prompts",
         }
         target_dir = Path(args.dir) if args.dir else agent_dirs[args.agent]
-        dst = target_dir / "codejury-review-repo.md"
+        dst = target_dir / "codejury-review.md"
         if dst.exists() and not args.force:
             print(f"{dst} already exists. Re-run with --force to overwrite it.", file=sys.stderr)
             return 1
         target_dir.mkdir(parents=True, exist_ok=True)
         dst.write_text(slash_command_file.read_text(encoding="utf-8"), encoding="utf-8")
         print(f"Installed slash command to {dst}")
-        print("Run it in the agent with: /codejury-review-repo <repository>")
+        print("Run it in the agent with: /codejury-review <repository or diff>")
         return 0
 
     if args.command == "review":

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/base.py

@@ -97,7 +97,7 @@ class Domain:
 class BackendUnavailable(RuntimeError):
     """A tool-backed seam was asked to work but its external tool is not installed. Raised,
     never swallowed into an empty result, so a missing toolchain is a loud failure and not a
-    silently clean review, invariant 3."""
+    silently clean review, invariant 4."""
 
 
 @dataclass(frozen=True, kw_only=True)

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/__init__.py

@@ -13,15 +13,22 @@ from pathlib import Path
 from codejury.domains.base import Domain
 from codejury.domains.evm.facts.slither import SlitherFacts
 
-# the repo-review pass lenses for contracts: each pass leads with one, the empty lens
-# reviews every class
+# the repo-review pass lenses for contracts: each pass leads with one class, the empty lens
+# reviews every class. A named lens is a reliable focused pass and the empty catch-all is not,
+# so every shipped contract class gets its own lens rather than relying on the catch-all.
 EVM_LENSES = (
     "access-control",
     "reentrancy",
-    "oracle-manipulation",
+    "oracle-price-manipulation",
     "accounting-precision",
     "signature-replay",
     "denial-of-service",
+    "bad-randomness",
+    "front-running",
+    "proxy-delegatecall",
+    "unchecked-low-level-call",
+    "unsafe-math",
+    "weird-erc20",
     "",
 )
 

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/facts/slither.py

@@ -4,7 +4,7 @@ Solidity compiler, availability is lazy-checked so importing the domain never ne
 heavy dependency, and slither itself is imported only inside extract.
 
 A backend that cannot run fails loud rather than returning empty facts that would read as a
-clean review, invariant 3. A missing toolchain raises BackendUnavailable, a compile error
+clean review, invariant 4. A missing toolchain raises BackendUnavailable, a compile error
 in the target propagates as the native slither error.
 """
 

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/index.md

@@ -19,6 +19,7 @@ the target. A finding's `category` is one of these ids.
 
 ### Economic and Accounting
 - `oracle-price-manipulation` spot price or balance as price, flash-loan assisted
+- `front-running` no minOut or deadline, sandwich, profitable action front-run
 - `accounting-precision` rounding, division before multiplication, ERC-4626 first-depositor inflation
 - `weird-erc20` fee-on-transfer, rebasing, ERC777 callback, received below the requested amount
 - `unsafe-math` unchecked-block overflow, narrowing downcast truncation
@@ -33,5 +34,5 @@ Report only real, exploitable, high-confidence issues with a concrete exploit pa
 fund or control impact. Do not report gas-optimization or style notes, floating-pragma or
 compiler advisories, dependency CVEs, or 0.8 checked-arithmetic overflow outside an
 `unchecked` block. The set is data: add a class by dropping a new
-`vulnerabilities/<id>.md` with the same frontmatter of id, title, impact, tags, and
-triggers, plus vulnerable and secure examples.
+`vulnerabilities/<id>.md` with the same frontmatter of id, title, impact, tags,
+triggers, and lens, plus vulnerable and secure examples.

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/access-control.md

@@ -1,10 +1,11 @@
 ---
 id: access-control
 title: Missing or Broken Access Control
+lens: access-control
 impact: CRITICAL
 tags: [swc-105, swc-115, access-control, fund-loss]
 aliases: [missing-access-control, broken-access-control]
-triggers: ["onlyOwner", "function mint", "function burn", "function withdraw", "selfdestruct", "tx.origin", "require(msg.sender", "_mint", "setOwner", "transferOwnership", "external", "public"]
+triggers: ["onlyOwner", "function mint", "function burn", "function withdraw", "selfdestruct", "tx.origin", "require(msg.sender", "_mint", "setOwner", "transferOwnership", "function approve", "blacklist", "isBlacklisted", "whenNotPaused", "external", "public"]
 ---
 
 ## Missing or Broken Access Control
@@ -16,6 +17,14 @@ The cause is a missing modifier, a modifier on the wrong function, an authorizat
 but not the right one. Gate every state-changing privileged function to the exact role,
 and use `msg.sender`.
 
+A security gate that some entrypoints enforce and a sibling omits is a broken invariant,
+report the gap even when the omitted path does not itself move value. A token with a
+blacklist, pause, or sanctions check that runs on `transfer` and `transferFrom` but not on
+`approve`, `permit`, or `increaseAllowance` lets a barred account still take part in the
+flow, so the control is not the invariant it claims. Enumerate the sibling entrypoints a
+stated invariant should cover and name the one missing the check, do not clear it because a
+later step looks gated.
+
 ### Vulnerable
 ```solidity
 function mint(address to, uint256 amount) external {   // no access control

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/accounting-precision.md

@@ -1,6 +1,7 @@
 ---
 id: accounting-precision
 title: Accounting and Precision Error
+lens: accounting-precision
 impact: HIGH
 tags: [accounting, rounding, precision, erc4626, fund-loss]
 aliases: [accounting, precision]

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/bad-randomness.md

@@ -1,6 +1,7 @@
 ---
 id: bad-randomness
 title: Insecure Randomness
+lens: bad-randomness
 impact: HIGH
 tags: [swc-120, randomness, fund-loss]
 aliases: [weak-randomness, predictable-random]
@@ -16,6 +17,12 @@ a validator can influence or withhold it, so the result is gamed and the payout
 Use a verifiable randomness source such as a VRF, or a commit-reveal scheme where the seed
 is fixed before it can be known.
 
+The timestamp-dependence variant is the same root cause applied to time, not selection: a
+proposer can nudge `block.timestamp` by a few seconds, so logic that gates an auction close,
+a vesting unlock, a deadline, or a reward rate on an exact `block.timestamp` comparison is
+manipulable at the margin. Use a tolerance band, a block-number gate, or an oracle time
+rather than trusting `block.timestamp` to the second.
+
 ### Vulnerable
 ```solidity
 function drawWinner(address[] calldata players) external {

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/denial-of-service.md

@@ -1,8 +1,9 @@
 ---
 id: denial-of-service
 title: Denial of Service
+lens: denial-of-service
 impact: HIGH
-tags: [swc-113, swc-128, dos, griefing, gas]
+tags: [swc-113, swc-128, dos, griefing, gas, fund-loss]
 aliases: [dos]
 triggers: ["for (", "while (", ".length", "push(", "transfer(", "revert", "external call", "unbounded", "for(uint", "selfdestruct"]
 ---

codejury-1.4.1/codejury/domains/evm/knowledge/vulnerabilities/front-running.md

@@ -0,0 +1,50 @@
+---
+id: front-running
+title: Front-Running and Slippage
+lens: front-running
+impact: HIGH
+tags: [swc-114, front-running, mev, sandwich, slippage, fund-loss]
+aliases: [mev, sandwich, slippage, frontrunning, front-run]
+triggers: ["swap", "minOut", "amountOutMin", "minAmountOut", "amountOutMinimum", "deadline", "getAmountOut", "addLiquidity", "removeLiquidity", "swapExactTokensForTokens", "0, path", "claim", "harvest"]
+---
+
+## Front-Running and Slippage
+
+A state-changing action is ordered against the victim in the mempool. A swap, deposit,
+or redeem that enforces no minimum output and no deadline executes at an attacker-chosen
+price, or a profitable action is observed and front-run. The classic shape is a sandwich,
+the attacker buys ahead of the victim, lets the victim's trade move the price, then sells
+into it. Bind every trade with a caller-supplied `minOut` and a `deadline`, and treat any
+value the transaction derives from a movable on-chain source as untrusted, see the
+oracle-price-manipulation class.
+
+### Vulnerable
+```solidity
+function zapIn(uint256 amountIn) external {
+    // minOut hardcoded to 0 and block.timestamp as the deadline, so a sandwich sets the price
+    uint256[] memory out = router.swapExactTokensForTokens(
+        amountIn, 0, path, address(this), block.timestamp
+    );
+    deposit(out[out.length - 1]);
+}
+```
+
+### Secure
+```solidity
+function zapIn(uint256 amountIn, uint256 minOut, uint256 deadline) external {
+    uint256[] memory out = router.swapExactTokensForTokens(
+        amountIn, minOut, path, address(this), deadline
+    );
+    deposit(out[out.length - 1]);
+}
+```
+
+### Not a Finding
+
+A trade that passes the caller's `minOut` and `deadline` straight through to the router
+is the expected control and is not reportable. Report it only when the slippage bound is
+hardcoded to 0, the deadline is replaced with `block.timestamp` so it can never expire,
+`minOut` is computed from a spot price read in the same call, or a privileged action's
+ordering grants a concrete and quantifiable fund advantage. A pure view function, an
+action with no economic ordering advantage, or generic mempool-visibility commentary is
+not a finding.

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/oracle-price-manipulation.md

@@ -1,6 +1,7 @@
 ---
 id: oracle-price-manipulation
 title: Oracle and Price Manipulation
+lens: oracle-price-manipulation
 impact: CRITICAL
 tags: [oracle, price-manipulation, flash-loan, fund-loss]
 aliases: [oracle, oracle-manipulation, oracle-validation, price-manipulation]

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/proxy-delegatecall.md

@@ -1,6 +1,7 @@
 ---
 id: proxy-delegatecall
 title: Proxy, Delegatecall, and Initializer Flaws
+lens: proxy-delegatecall
 impact: CRITICAL
 tags: [swc-112, delegatecall, proxy, initializer, upgrade, fund-loss]
 aliases: [delegatecall, unprotected-upgrade]

codejury-1.4.1/codejury/domains/evm/knowledge/vulnerabilities/reentrancy.md

@@ -0,0 +1,61 @@
+---
+id: reentrancy
+title: Reentrancy
+lens: reentrancy
+impact: CRITICAL
+tags: [swc-107, reentrancy, fund-loss]
+aliases: [read-only-reentrancy]
+triggers: [".call{value", ".call(", "transfer(", "send(", "external call", "balances[", "withdraw", "nonReentrant", "safeTransfer", "onERC721Received", "tokensToSend", "tokensReceived", "ERC777", "buyout", "before state", "get_virtual_price", "getReserves", "getRate", "sharePrice", "view returns", "balanceOf(address(this))"]
+---
+
+## Reentrancy
+
+An external call hands control to the callee before the contract finishes updating its
+own state, so the callee can call back in and act on the stale pre-update state. The
+classic form drains a balance by re-entering a withdraw before the balance is zeroed.
+Cross-function reentrancy re-enters a different function that shares the same state, and
+read-only reentrancy reads a view mid-update from another protocol. The read-only form
+needs no state write in the reentered call: a price or share view such as a Curve
+`get_virtual_price`, a Balancer `getRate`, or a `getReserves` or `balanceOf(address(this))`
+spot read returns a stale value while a withdraw or exit has sent value but not yet synced
+its reserves, and a consumer that prices collateral off that view is fooled. Write state
+before the external call, or guard with `nonReentrant`, and remember a guard on the mutating
+function does not stop the cross-contract read-only form, the view must be consistent at the
+moment of the external call.
+
+A token transfer is an external call too. An ERC777 token runs a `tokensToSend` hook on
+the sender and a `tokensReceived` hook on the recipient, and other tokens add their own
+transfer callback, so a plain `transfer` or `safeTransfer` of an ERC20 can hand control to
+an attacker exactly like a raw `call`. Treat any token whose address is not a fixed trusted
+constant as possibly hook bearing and check every token-move path for reentrancy, not only
+the `call{value}` paths. Clearing a path because the token is assumed to be a normal ERC20
+with no hook is an assumed off-file control unless the token set is pinned to a known
+allowlist, so keep the finding, see the recall red line.
+
+Ordering effects before interactions in the one function under review is not enough on its
+own. A transfer hook can reenter a different function that reads or writes the same position,
+loan, or reserve while this flow is only half finished, the cross-function form, so trace
+where control can go during every transfer and check the whole flow's invariants, not just
+the local ones. In a lending, auction, or buyout flow that pays the current holder before it
+finalizes the position's terms, that payout is the callback window, so audit the order of
+the payout against the state writes.
+
+### Vulnerable
+```solidity
+function withdraw() external {
+    uint256 bal = balances[msg.sender];
+    (bool ok, ) = msg.sender.call{value: bal}("");   // call before the state update
+    require(ok);
+    balances[msg.sender] = 0;                          // too late, attacker reentered
+}
+```
+
+### Secure
+```solidity
+function withdraw() external nonReentrant {
+    uint256 bal = balances[msg.sender];
+    balances[msg.sender] = 0;                          // effects before interaction
+    (bool ok, ) = msg.sender.call{value: bal}("");
+    require(ok);
+}
+```

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/signature-replay.md

@@ -1,6 +1,7 @@
 ---
 id: signature-replay
 title: Signature Replay and Malleability
+lens: signature-replay
 impact: HIGH
 tags: [swc-117, swc-121, signature, replay, eip712, fund-loss]
 aliases: [replay, replay-attack]

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/unchecked-low-level-call.md

@@ -1,10 +1,11 @@
 ---
 id: unchecked-low-level-call
 title: Unchecked Low-Level Call
+lens: unchecked-low-level-call
 impact: HIGH
 tags: [swc-104, low-level-call, return-value, fund-loss]
 aliases: [unchecked-call, unchecked-return]
-triggers: [".call(", ".call{value", ".delegatecall(", ".send(", "transfer(", "bool success", "bool ok", "(bool", "safeTransfer", "returndata"]
+triggers: [".call(", ".call{value", ".delegatecall(", ".send(", "transfer(", "bool success", "bool ok", "(bool", "safeTransfer", "returndata", "returndatacopy", "abi.decode(returndata", "excessivelySafeCall"]
 ---
 
 ## Unchecked Low-Level Call
@@ -17,6 +18,12 @@ raw ERC-20 `transfer` on a token that returns false on failure, or returns nothi
 be checked or wrapped with SafeERC20. Check every low-level return, or use a wrapper that
 reverts.
 
+The mirror risk is trusting the returned data rather than the boolean: a callee can return
+an enormous bytes blob so that copying it, an implicit `returndatacopy` or an
+`abi.decode(returndata, ...)`, burns all forwarded gas and griefs the caller, the return-bomb.
+When the return payload is attacker-influenced, cap the copied size or use an
+`excessivelySafeCall` style helper, and never let a callee's return data dictate gas.
+
 ### Vulnerable
 ```solidity
 function payout(address to, uint256 amount) external {

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/unsafe-math.md

@@ -1,6 +1,7 @@
 ---
 id: unsafe-math
 title: Unchecked Math and Unsafe Cast
+lens: unsafe-math
 impact: HIGH
 tags: [swc-101, overflow, downcast, fund-loss]
 aliases: [unchecked-math, unsafe-cast, downcast-truncation]

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/knowledge/vulnerabilities/weird-erc20.md

@@ -1,6 +1,7 @@
 ---
 id: weird-erc20
 title: Weird ERC20 Behavior
+lens: weird-erc20
 impact: HIGH
 tags: [fee-on-transfer, rebasing, erc777, accounting, fund-loss]
 aliases: [fee-on-transfer, deflationary-token, rebasing-token, erc777-hook]

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/playbook/slash-command.md

@@ -1,7 +1,41 @@
 ---
-description: Run a codejury whole-protocol smart contract security review, interactively, by fanning out per contract
+description: Run a codejury smart contract security review of a diff or a whole repository
 ---
-Run a codejury whole-protocol smart contract security review of: $ARGUMENTS
+Run a codejury smart contract security review of: $ARGUMENTS
+
+First decide which path $ARGUMENTS names, the two are different tools, do not mix them.
+
+- DIFF REVIEW when $ARGUMENTS is a unified diff file such as a `.diff` or `.patch`, a single
+  file of diff text, or a git range such as `origin/main...HEAD`. This path is fully coded,
+  you run one command and relay its report, there is no fan-out and no workspace.
+- REPO REVIEW when $ARGUMENTS is a directory, a whole protocol to audit. This path is the
+  fan-out you orchestrate, follow the numbered steps under Repo Review.
+
+## Diff Review
+
+Run the coded engine and relay its report. There is nothing for you to judge, the engine
+chunks the diff, runs its passes, filters, and prints the findings.
+
+```
+codejury review diff --file <the diff file> --domain evm
+```
+
+For a git range instead of a file, drop `--file` and pass the range, with `--repo` if the
+repository is not the current directory:
+
+```
+codejury review diff --repo <repo dir> --git-range origin/main...HEAD --domain evm
+```
+
+If `codejury` is not on PATH it is a pip-installed console script, so activate the project
+venv first, for example `. .venv/bin/activate`, or run `python -m codejury`.
+
+Relay the report as it prints. A failed, rate-limited, blank, or error-exited run is a
+failed review, not a clean pass, surface the error and never report zero findings from a
+broken run. A non-zero exit means a finding hit the severity gate or the audit degraded, say
+which. Then stop, Diff Review does not use the units, the workspace, or the gate below.
+
+## Repo Review
 
 You are the orchestrator, not the reviewer. Recall comes from fanning out: the tool gives
 you a deterministic unit worklist, you run one focused sub-review per contract in parallel,

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/playbook/unit-review.md

@@ -64,6 +64,11 @@ of a named guard:
   moves more of the holder's balance than was approved.
 - **Signatures**: is a signed privileged message bound to a nonce, a chainid, and a domain
   separator, the signer checked nonzero? A signature alone is replayable.
+- **Failure mode**: when a call or a guard fails, does the path fail closed or fail open? A
+  low-level `call`, `delegatecall`, or `send` whose returned success bool is not checked lets
+  execution continue as if it succeeded, and a `try/catch` whose catch branch proceeds rather
+  than reverting leaves the contract in a partly updated state. Confirm a failed external call
+  or check reverts the transaction rather than silently continuing.
 - **Trusted-source**: a value is not safe because a caller you treat as trusted set it, if
   that caller is an arbitrary external account or contract.
 - **Seeded invariant**: `inventory/_invariants.md` may name a property the operator asserts

{codejury-1.3.0 → codejury-1.4.1}/codejury/domains/evm/poc.py

@@ -4,13 +4,13 @@ compile and run it, turning a model claim into a reproduced fact. Behind the cod
 extra and a Foundry toolchain, availability is lazy-checked so importing the domain never
 needs forge.
 
-Safety is the hard contract, invariant 4. A PoC runs only against a local fork or a dev
+Safety is the hard contract, invariant 6. A PoC runs only against a local fork or a dev
 node, never a production system. It never holds a real private key, never broadcasts a
 transaction, and takes no destructive action without explicit operator approval.
 
 The generation and run logic lands once Foundry is validated on a real target. Until then
 this is the wired seam: it reports availability honestly and fails loud when asked to
-verify without the tool, never silently confirming or refuting a finding, invariant 3.
+verify without the tool, never silently confirming or refuting a finding, invariant 4.
 """
 
 from __future__ import annotations