Skip to content

1.2.0

Latest

Choose a tag to compare

@nrzz nrzz released this 19 Nov 04:35
0d7e99b
  • claude-hook-bench list, run --http and /hook-bench:check warn when an http hook's header uses an environment variable that allowedEnvVars does not list, which Claude Code fills with an empty string. There is one warning for each reference, naming the header and the variable (the header "X-Team" uses $TEAM, which allowedEnvVars does not list: Claude Code sends an empty string for it), so $TOKEN-$SECRET gives two. A hook with no allowedEnvVars at all keeps its earlier warning, and an allowedEnvVars entry that no header uses is a note, not a warning.
  • The check and the request share one pattern for a reference (ENV_REF in src/http.mjs), so they cannot disagree about what counts as one. The README's findings table has a row for http hooks.
  • Contributed by @madhavidayma21 in #4, for the good first issue #3. The pull request's tests ran on Windows, macOS and Linux with Node 18 to 24, and the real-binary checks against Claude Code on Ubuntu and macOS, before the merge.

The next good first issue is #5: a finding for an allowedEnvVars entry that is not a bare variable name ("$POLICY_TOKEN" instead of "POLICY_TOKEN"), which can never match a header.

See the README to set it up, and CHANGELOG.md for every version.