Repository navigation
0.3.1: security and data-loss fixes from the post-launch audit - #1
Open
cloudhobbit wants to merge 3 commits into
Open
cloudhobbit wants to merge 3 commits into
cloudhobbit wants to merge 3 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- GitLab: send the token as `Authorization: Bearer`, which fetch drops on a cross-origin redirect; PRIVATE-TOKEN followed an SSO/proxy redirect. - GitLab: GITLAB_TOKEN / GITLAB_ACCESS_TOKEN go only to gitlab.com, the host in GITLAB_HOST, or the GitLab CI job's own instance, not to any GitLab-looking host a checkout's origin names. - GitHub: a host that isn't recognisably github.com or GHE.com (an --api-url on an intranet name) gets the enterprise tokens, never GH_TOKEN / GITHUB_TOKEN. - ssh.github.com and :443 normalise to their host. Found in the post-launch audit; each has a regression test (the redirect one with two real local servers). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Incremental fetches keep everything created in the window (keepSince), not only since the last fetch: old comments edited, and PRs first listed (e.g. updated during a --time-budget pause), after the previous fetch started were dropped for good. - GitLab corpora are stamped with the fetch's start time. - The MCP index child always settles: one killed by a signal or OOM made every later call for the repo hang. - rules status: no top-50 cut before the window/path filters. - run --demo runs the demo; other commands refuse --demo (it was ignored and a real run started). - AGENTS.md: the generator and `export` use separate markers; cursor --force skips files export wrote. - "$" in rule text stays literal when managed blocks are rewritten. - --llm rules use the parsed examples heading; slugs never end in "-"; generate records its rules in the manifest. - Case-insensitive owner/repo matching; rule sources read GHES/GitLab PR links. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Fixes from the post-launch audit. 0.3.0 was never published to npm, so 0.3.1 becomes the first npm release.
Security
Authorization: Bearer, whichfetchdrops on a cross-origin redirect. A regression test uses two real local servers.GITLAB_TOKENwas sent to any GitLab-looking host named inorigin. It now goes only to gitlab.com, toGITLAB_HOST, or to the GitLab CI job's own instance.--api-urlon an unrecognised host receivedGITHUB_TOKEN. Such hosts now get the enterprise tokens only.Data loss and correctness
--time-budgetpause. They now keep everything created in the window.rules statusfalsely flaggedno-recent-support.run --demostarted a real run.run --format agents|cursorandexportoverwrote each other.$in rule text was mangled when managed blocks were rewritten.--llmrules lost their cited examples.-, and the tool couldn't read them back.generatedidn't record the rules it wrote.ssh.github.comand:443remotes are treated as github.com;Each fix has a regression test (375 → 386 tests). The evals are unchanged, and
audit:allandclaude plugin validatepass. See the CHANGELOG[Unreleased]section.🤖 Generated with Claude Code