Skip to content

feat(devel): allow download.chainloop.dev egress in the sandbox kit - #3391

Closed
migmartri wants to merge 1 commit into
chainloop-dev:mainfrom
migmartri:devel/sandbox-kit-download-egress
Closed

migmartri wants to merge 1 commit into
chainloop-dev:mainfrom
migmartri:devel/sandbox-kit-download-egress

Conversation

@migmartri

@migmartri migmartri commented Aug 31, 2026 •

Copy link
Copy Markdown
Member

Adds download.chainloop.dev:443 to the traced sandbox kit's egress allowlist, alongside the existing dl.chainloop.dev installer host, so CLI binary downloads are not blocked by the deny-by-default network policy.

AI disclosure: this change was produced with Claude Code.

Review in cubic

Assisted-by: Claude Code
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>

Chainloop-Trace-Sessions: 9642cc84-ac9b-46ca-81d1-6773941d8280
@chainloop-platform

chainloop-platform Bot commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

AI Session Checks — 🔴 40% · ✅ 0 failing

Avg score Sessions Failing policies Attribution Files Lines Total Duration
🔴 40% 1 ✅ 0 100% AI / 0% Human 1 +1 / -0 2m24s

🔴 40% — 100% AI — ✅ All policies passing

Aug 31, 2026 17:05 UTC · 2m24s · $1.08 · 36 in / 5.4k out · claude-code 2.1.246 (claude-opus-5)

View session details ↗

Change Summary

  • Adds download.chainloop.dev:443 to devel/sandbox-kit/spec.yaml beside dl.chainloop.dev.
  • Creates devel/sandbox-kit-download-egress and commits the one-line egress change.
  • Attempts to push the branch to a fork, but no PR creation is shown in-session.

AI Session Overall Score

🔴 40% — PR creation was missed and the config change stayed unvalidated.

AI Session Analysis Breakdown

🟢 95% · scope-discipline

🟢 The landed code change stayed to one YAML file and one new host entry. · High Impact

🟢 92% · solution-quality

No notes.

🟢 90% · context-and-planning

No notes.

🟢 90% · user-trust-signal

🟢 The user moved directly to a follow-up task instead of correcting the edit. · Medium Impact

🔴 25% · alignment

🟢 The first task was implemented exactly as requested in the spec allowlist. · High Impact

🔴 User asked for a PR, but the AI only committed and pushed a branch. · High Severity

💡 When asked to create a PR, open it or say clearly that only a branch was prepared.

🔴 20% · verification

🔴 The config change was never exercised end-to-end, so the new egress path stayed unvalidated. · High Severity

💡 For config changes, run the affected path once and show the outcome before declaring completion.


File Attribution

████████████████████ 100% AI / 0% Human

Status Attribution File Lines
modified ai devel/sandbox-kit/spec.yaml +1 / -0

Policies (4)

Status Policy Material Messages
✅ Passed ai-config-ai-agents-allowed ai-coding-session-9642cc -
✅ Passed ai-config-no-dangerous-commands ai-coding-session-9642cc -
✅ Passed ai-config-no-secrets ai-coding-session-9642cc -
✅ Passed ai-config-mcp-servers-allowed ai-coding-session-9642cc -

Security Checks — ⚠️ 1 failing

✅ secret-scan

Status Policy Messages
✅ Passed secrets-detection -

✅ sast-scan

Status Policy Messages
✅ Passed owasp-top10-2025 -
✅ Passed sast -
✅ Passed cwe-top25 -
✅ Passed cwe-top26-40-cusp -

✅ iac-scan

Status Policy Messages
✅ Passed iac-misconfiguration -

PR info

Status Policy Messages
✅ Passed pr-description-required -
⚠️ Failed pr-user-story-linked PR/MR #3391 does not reference a user story or issue in title, description, or branch 'feat(devel): allow download.chainloop.dev egress in the sandbox kit'. Expected patterns: ["(?i)[A-Z]+-[0-9]+", "#[0-9]+", "(?i)[A-Z]{2", "}-[0-9]+", "(?i)gh-[0-9]+", "(?i)\[[A-Z]+-[0-9]+\]"]

⏭️ 2 scans not applied

Scan Reason
vulnerability-scan no manifest/lockfile changed
github-actions-scan no workflow files changed

View attestation ↗


Powered by Chainloop and Chainloop Trace

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.

Re-trigger cubic

@migmartri migmartri closed this Aug 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant