Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[integrity-audit] Integrity Filtering Audit — 2026-10-15

Open
  • Is something wrong?
#14,937 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
github-actions, go, wasm
Domain
devops, security

Research direction

The only concrete problem is the warning that the WASM compile cache at /tmp/gh-aw/wazero-cache failed with permission denied and fell back to in-memory compilation, which is logged during guard startup. The audit's own recommendations (fix the runner's cache directory permissions, or make the DIFC logs downloadable) are operational, not code changes, and need repository and runner access. A newcomer would have to confirm the desired outcome with maintainers before starting.

Written by the indexing model from the issue text.

Description

automation integrity-audit
Integrity Filtering Audit — github/gh-aw-mcpg

Audit period: Last 24 hours (sampled from the newest 30 completed runs, all from 05:33–05:54 UTC)
Runs analyzed: 30 listed; 1 agent job log inspected in depth (Issue Monster, run 38688320210)
Runs with artifacts: Artifact listings reviewed for 2 runs; artifact contents could not be downloaded (see Limitations)

Findings Summary
Severity Count Description
🔴 Critical 0 No data leaks or guard bypass observed
🟡 Warning 1 wazero-cache directory creation permission denied (in-memory fallback)
🟢 Info 3 Limited audit depth; many skipped runs; unrelated CI failures
Critical Findings

None observed in the inspected log.

Warnings

W-A: WASM compilation cache fallback (Issue Monster run 38688320210, agent job 116268604043)
[WARN] [startup] Falling back to in-memory WASM compilation cache after "/tmp/gh-aw/wazero-cache" failed: ... permission denied. Not a DIFC failure, but guard startup does a full WASM compile each time. Check directory ownership/permissions for the cache dir in the workflow runner.

Direct API bypass (W-1): none detected. The only api.github.com references in the agent job log are gateway/proxy-internal (Resolved GitHub API URL, githubhttp:client GET /repos/github/gh-aw for sink visibility verification). No chatgpt.com/openai.com references and no firewall block/deny entries.

Informational
  • Issue Monster agent job: guard registered for safeoutputs (write-sink, sink-visibility=public; runtime verification passed: configured=public, actual=public). GitHub proxy started with difcMode=filter and allow-only policy min-integrity=approved. ~159 DIFC-related log lines; no wasm error:, WASM guard trap, guard not initialized, unknown REST endpoint, or Phase ... failed entries. Agent started with empty secrecy/integrity tags as expected.
  • forcePublicRepos: GITHUB_REPOSITORY not set — skipping logged in the proxy stage (informational; policy was supplied explicitly).
  • Of 30 runs, 7 were skipped (Agentic Workqueue, AI Moderator, Squad, Q, Squad implement x2) and 5 failed (CJS, PR Code Quality Reviewer, Doc Build - Deploy x2, CGO x2, CWI) — these are CI/PR workflows; not assessed for DIFC.
  • Agentic runs observed as successful: Daily VulnHunter Scan (38688480314), Daily Safe Outputs Conformance Checker, Issue Monster, Daily PR Code Quality Review, Failure Investigator (6h), PR Sous Chef, Daily Trajectory Grader Implementer.
Runs Analyzed
Run Workflow Branch Agent Invoked DIFC Events Firewall Blocks Status
38688320210 Issue Monster main ✅ ~159 log lines (job log) 0 ⚠️ (cache warning)
38688480314 Daily VulnHunter Scan main ✅ (artifacts listed only) not inspected not inspected ✅
38688391715 Daily Safe Outputs Conformance Checker main ✅ not inspected not inspected ✅
Others see Info — — not inspected not inspected —
Limitations

gh is unauthenticated in this sandbox and the GitHub MCP tools expose artifact listings but not downloads of rpc-messages.jsonl; only the tail (last 1500 lines) of a single agent job log was analyzed. Per-run tag-scoping (approved:owner/repo) and filtered-count ratios could not be verified. The step-summary table was not produced.

Recommendations
  1. Make rpc-messages.jsonl / mcp-gateway.log available to the audit (e.g. a job-summary DIFC digest or a download-capable token) so tag scoping and filter ratios can be verified.
  2. Fix /tmp/gh-aw/wazero-cache permissions in the runner to restore the disk-backed WASM compile cache.
  3. No W-1 workflows to investigate; for reference, reusable routing constraint language lives in shared/mcp-api-routing.md.

Generated by Integrity Filtering Audit · copilot · auto · 39.5 AIC · ⊞ 13.3K · ◷

  • expires on Oct 22, 2026, 5:58 AM UTC
Dominant language
Go
Stars
181
Forks
53
Avg merge
7h 27m
Merged PRs (30d)
204

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-aw-mcpg

All issues in github/gh-aw-mcpg

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.