chore(master): release 0.22.1 - #210
Merged
pszymkowiak merged 1 commit intoFeb 19, 2026
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--master--components--rtk
branch
3 times, most recently
from
February 19, 2026 14:52
dbdd64b to
379f601
Compare
github-actions
Bot
force-pushed
the
release-please--branches--master--components--rtk
branch
from
February 19, 2026 14:52
379f601 to
999e26b
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
thehoff
pushed a commit
to thehoff/contextcrawler
that referenced
this pull request
May 14, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
thehoff
added a commit
to thehoff/contextcrawler
that referenced
this pull request
Jul 14, 2026
…i#210) The rtk-ai#191 rework left `suppresses_finding_for_command` returning `all_interpreter_pipe_sinks_are_data_mode(cmd) || python_module_is_data_parser(cmd)`. The second arm scanned the ENTIRE command for `python -m json.tool`, so a bare json.tool ANYWHERE cleared a genuine pipe_to_interpreter finding for an unrelated malicious pipe — re-opening the exact bypass rtk-ai#191 closed (shipped in 0.4.2). Council-confirmed 4/4. `all_interpreter_pipe_sinks_are_data_mode` already classifies `python3 -m json.tool` as a data-mode sink under the source gate, so the OR was redundant as well as unsafe. Removed it and the now-dead `python_module_is_data_parser`. Empirical (live hook): `printf evil | sh; python3 -m json.tool x` now asks; `cat data.json | python3 -m json.tool` still passes. Refs: rtk-ai#210 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3SAimSBwPUp4MkRXaYXSU
thehoff
added a commit
to thehoff/contextcrawler
that referenced
this pull request
Jul 14, 2026
Security release: rtk-ai#210 (json.tool bypass regression from 0.4.2), rtk-ai#229 (env-prefix proxy-disable injection), rtk-ai#224 (GLOB project-history leak), rtk-ai#221 (trust symlink secret-exfil), rtk-ai#223 (unscrubbed parse-failure error). All council-gated. From the codex-5.6-max sweep + 5-voice audit (rtk-ai#210-rtk-ai#233). See CHANGELOG. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3SAimSBwPUp4MkRXaYXSU
thehoff
added a commit
to thehoff/contextcrawler
that referenced
this pull request
Jul 14, 2026
Large security release completing the codex-5.6-max sweep + 5-voice council audit (rtk-ai#210-rtk-ai#233): rtk-ai#219/rtk-ai#220 (hook-tamper validation rebuild + trust store), rtk-ai#225 (non-Claude handler gating), rtk-ai#212-rtk-ai#218/rtk-ai#230 (permission gate + lexer), rtk-ai#211 (Tirith deadlock), rtk-ai#222 (config injection), rtk-ai#226/rtk-ai#232/rtk-ai#233 (filter engine). The two big clusters were authored by the Codex worker in isolated worktrees, driver-verified and non-author-council-reviewed. See CHANGELOG. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3SAimSBwPUp4MkRXaYXSU
thehoff
added a commit
to thehoff/contextcrawler
that referenced
this pull request
Jul 14, 2026
Supply-chain gate hardening (rtk-ai#227/rtk-ai#228/rtk-ai#231) — completes the security audit register rtk-ai#210-rtk-ai#233. Three Codex-authored rounds, driver-verified + non-author council-reviewed. Install-detection evasions, fail-open verdicts, network-trust MITM bypass, recursion/launcher/lockfile gaps, 429 DoS, credential-safe findings. Gate remains default-off. See CHANGELOG. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K3SAimSBwPUp4MkRXaYXSU
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.22.1 (2026-02-19)
Bug Fixes
This PR was generated with Release Please. See documentation.