Uh oh!
There was an error while loading. Please reload this page.
[compiler-threat-spec] spec: bump compiler-threat-detection-spec to v1.0.14 (CTR-020) - #42169
Merged
pelikhan merged 1 commit intoJun 29, 2026
Merged
Conversation
Add CTR-020 Conditional Import Security covering the compiler-level
rejection of imports.if fields (pkg/parser/import_bfs.go). Conditional
imports were removed because they can alter workflow setup and security
posture at runtime.
Also:
- Extend CTR-010 mapping with runtime_import_validation.go
(validateRuntimeImportFiles enforces expression allowlist in
{{#runtime-import}} macro targets)
- Update Section 7.2 mapping audit to 2026-06-29 covering PR #42146
- Add spec-to-implementation sync table row for v1.0.14
Reviewed threats:
- CTR-020 (new): imports.if rejection — uncovered → implemented in
pkg/parser/import_bfs.go, test: TestParseImportSpecsFromArray_RejectsIfField
- Sandbox validation consolidation (sandbox_validation.go) → strengthens
CTR-004; already covered by mapping pattern pkg/workflow/sandbox_validation*.go
- Runtime import expression validation (runtime_import_validation.go) →
extends CTR-010 coverage
- network-isolation → sudo rename → refactoring only, no new CTR rule
- mcpg/firewall dependency bumps → runtime-only, outside compiler scope
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>pelikhan
approved these changes
Jun 29, 2026
pelikhan
deleted the
daily-threat-spec-optimizer/2026-06-29-d5c86b85670ae3d3
branch
June 29, 2026 05:32
ContributorAuthor
🎉 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 freeto 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.13 to v1.0.14, adding CTR-020 Conditional Import Security as a new mandatory detection rule.
Changes
New rule — CTR-020 Conditional Import Security (Section 5.1)
imports:entries that contain aniffield at compile time.{{#if ...}}{{#runtime-import? ...}}{{/if}}for experiment-specific prompt imports.pkg/parser/import_bfs.go(parseImportSpecsFromArray).pkg/parser/import_bfs_test.go(TestParseImportSpecsFromArray_RejectsIfField).New test — T-CTR-020 (Section 8.1)
imports:list with an object entry containing aniffield.CTR-010 mapping extended (Section 7.1)
pkg/workflow/runtime_import_validation.go(validateRuntimeImportFiles) added to CTR-010 Expression Safety Allowlist mapping.Spec-to-implementation sync table updated (Section 2)
1.0.14row: minimum gh-aw binaryv0.72.1(or newer).Mapping audit updated (Section 7.2)
Files Changed
specs/compiler-threat-detection-spec.mdCompatibility
Minimum gh-aw binary version remains
v0.72.1(or newer). No lock-file format changes; the newimports.ifrejection is a compiler parse-time error.References: