Repository navigation
fix(coding-agent): harden publication security - #262
Merged
Merged
Conversation
- Restrict model publication to trusted main sources and isolate upload credentials - Disable unsafe issue analysis and update vulnerable production dependencies - Require an explicit retained-artifact audit before changing source visibility
This reverts commit 8e8ada3.
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.
Summary
Prevent model publication from fork CI or arbitrary manual source refs, disable credential-bearing issue analysis, and patch the three reported production dependency vulnerabilities.
Reasoning
Successful CI and maintainer authorization do not establish a safe boundary for executing untrusted code or issue content with publication credentials.
Source hosting remains private pending a broader publication review.
Changes
Live settings were also hardened: main requires review and CI without bypasses; release tags cannot be modified or deleted; tag creation is restricted to repository admins, currently Pepps233 only.
Secret scanning, push protection, Code Security, Dependabot security updates, and CodeQL default setup are enabled.
The model-upload environment permits only the main branch.
Issue analysis is disabled in GitHub immediately.
Deployment reviewers remain blocked by the private repository's billing plan.
The existing direct-push release procedure needs a PR-based path under main protection.
The full dependency audit still reports nine development-only findings; the production audit is clean.
A targeted scan of all 27 retained private-named artifacts and their 18 associated log archives inspected 65,280 files without matching the selected secret patterns.
This does not cover all retained artifacts, historical runs, linked gists, or all secret formats and is not publication clearance.
Testing
npm run checkpassed.node --test scripts/*.test.mjs: 350 tests passed.npm audit --omit=dev: zero vulnerabilities.