mcp-searxng: security scan hung for 6 hours, image never published
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Description
The ghcr.io/stacklok/dockyard/npx/mcp-searxng:0.8.0 image was never published after PR #383
merged. The "Run MCP Security Scan" step hung for ~6 hours (16:30 to 22:35 UTC) before being
killed by the job timeout.
Failed run: https://github.com/stacklok/dockyard/actions/runs/21783187683/job/62850395173
The subsequent push (brightdata update, run 21793482090) completed its security scan successfully,
so the scan infrastructure itself is working. The hang appears specific to mcp-searxng.
The spec includes mock_env for SEARXNG_URL pointing to http://example.com. It's possible the
scan is attempting a real connection to this URL and blocking on the response.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failed “Run MCP Security Scan” job from run 21783187683 and compare it with the successful scan in run 21793482090. Inspect the mcp-searxng spec’s mock_env value for SEARXNG_URL and determine why the scan hangs; done means the scan completes and the 0.8.0 image is published after PR #383.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100