[compiler-threat-spec] spec: bump compiler threat detection spec to v1.0.16#45178
Merged
pelikhan merged 1 commit intoJul 13, 2026
Merged
Conversation
Daily optimizer run 2026-07-13. Review window: commit fe21742 (fix: emit sbx credential refresh step before agent execution, merged 2026-07-12). Security-relevant items evaluated: 1. docker-sbx microVM runtime support: compiler enforces sudo: true, compatible topology, and min AWF version — covered by CTR-004. Strict mode sudo deprecation path correctly exempts docker-sbx. 2. Docker Hub secrets via env var binding (DOCKER_PAT_VAL, DOCKER_USERNAME_VAL): CTR-017 compliant. 3. Credential refresh step before agent execution: security improvement, no new threat class. No new CTR rules required. All CTR-001 through CTR-021 remain fully covered with implementation references and test coverage. Changes: - Bump Version to 1.0.16 - Add v1.0.16 row to Section 2 spec-to-implementation sync table - Update Section 7.2 mapping audit with 2026-07-13 findings - Add v1.0.16 change log entry Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pelikhan
deleted the
daily-threat-spec-optimizer-2026-07-13-1695f9034d0e7980
branch
July 13, 2026 06:28
This was referenced Jul 13, 2026
Contributor
Author
|
🎉 This pull request is included in a new release. Release: |
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
Bumps the compiler threat detection specification from v1.0.15 to v1.0.16. This is a spec-only change; no production Go code is modified.
Changes
specs/compiler-threat-detection-spec.md1.0.15→1.0.161.0.16row added.v0.72.1(unchanged from 1.0.15).docker-sbxCTR-004 enforcement (sudo: truerequired,arc-dindrejected, minimum AWF version enforced) and the credential-refresh step as a security improvement with no new.lock.ymlconstraint.c9361ed(2026-07-05) to commitfe21742(fix: emit sbx credential refresh step before agent execution, merged 2026-07-12). Three items evaluated:docker-sbxmicroVM runtime support (pkg/workflow/docker_sbx_install.go,pkg/workflow/sandbox_validation.go): enforcessudo: true, compatible runner topology, and minimum AWF version; covered by CTR-004; no new CTR rule.DOCKER_PAT_VAL,DOCKER_USERNAME_VAL): compliant with CTR-017 safe binding pattern; no new CTR rule.sbx createis a security improvement with no new threat class; no new CTR rule.1.0.16 (2026-07-13)entry added.Impact
v0.72.1.lock.ymlsemanticsMotivation
Formalises the security audit of
fe21742, which emits aRefresh sbx credentialsstep before AWF agent execution in thedocker-sbxsandbox runtime. The spec records that no new threat classes were introduced and that all evaluated patterns are covered by existing CTR rules.