Harden CI/security: CodeQL + Dependabot + coverage gate + SECURITY (pilot)#1
Merged
Conversation
…tions to SHAs Hardens the repo's quality/security surface and makes it legible in the GitHub UI: - codeql.yml: security-extended SAST on push / PR / weekly (populates Security tab) - dependabot.yml: weekly pip + github-actions update PRs - ci.yml: coverage-gated matrix (--cov-fail-under=90; currently 96% covered) plus a self-contained coverage badge + per-PR coverage comment; least-privilege permissions: block; all actions pinned to full commit SHAs - SECURITY.md: private vulnerability disclosure policy - README: CodeQL + coverage badges and a "this repo gates itself" section - .gitignore: ignore coverage artifacts Pilot for a uniform standard rolling to rag-guard, agent-cost-attribution, fleet-mode, and bow. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
…esolves paths The coverage badge/comment job failed with 'No source for code' because the action runs its own coverage binary against absolute paths from the runner. relative_files=true (the action's documented requirement) stores relative paths. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…SHAs QC follow-ups from the independent review: - add tests for get_gate() lookup + fail-closed unknown-gate error (gate.py 100%) - pin actions/checkout, setup-python, and gh-action-pypi-publish in publish.yml to commit SHAs, so 'every Action is SHA-pinned' is literally true - README: coverage note 96% -> 97% Co-Authored-By: Claude Opus 4.8 <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.
What
Pilot of a uniform reliability/security standard for the flagship repos. This makes the repo's quality bar visible in the GitHub UI (Security tab, required checks, badges) while genuinely hardening it.
Added
security-extended) on push / PR / weekly → populates the Security tabpip+github-actionsupdate PRsci.ymlnow runs--cov-fail-under=90across Python 3.11–3.13 (measured 96%), plus a self-contained coverage badge + per-PR comment (no third-party service)permissions:blocks; every Action pinned to a full commit SHAVerified locally
pytest --cov=agent_gate --cov-fail-under=90→ pass, 96%, 17 testscoverage run -m pytest && coverage report) → passNote
The coverage badge resolves once this merges to
main(the badge data branch is created on the first main run). Branch protection (require CI + CodeQL green) will be enabled after merge.🤖 Generated with Claude Code