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

Windows x64 preview (0.6.3): please test

Open Beginner friendly
  • Is something wrong?
#334 7 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp, powershell
Domain
cli, operating-systems, release, testing-qa

Research direction

Download ripwire-0.6.3-windows-x64.zip and its checksum from the v0.6.3 release, then follow the PowerShell checklist in this issue. Verify the version, cached XML output, doctor results, and optional MCP installer; done means reporting the Windows version, CPU, version line, and an ok or failure result for each step.

Written by the indexing model from the issue text.

Description

Hi @lennix1337, @elsRobin, @antoniojosedev, @matbeedotcom: you're the people who have run ripwire on Windows, so
we'd love your help with one thing.

0.6.3 is out, and it ships a native Windows x64 binary (ripwire.exe) as a preview. CI builds it on windows-latest,
unzips it and runs it: --doctor, the cache, an MCP handshake, and its output compared byte for byte with the
Linux binary's. But none of us has a Windows machine, and CI can't tell us about SmartScreen, antivirus, older
Windows versions or your real repos. Ten minutes on your machine would tell us more than any CI run.

What to download: from https://github.com/redhat-et/ripwire/releases/tag/v0.6.3, download
ripwire-0.6.3-windows-x64.zip and ripwire-0.6.3-windows-x64.zip.sha256 into the same folder.

Checklist (PowerShell, in the folder you downloaded to):

  1. Verify: (Get-FileHash .\ripwire-0.6.3-windows-x64.zip).Hash -eq (Get-Content .\ripwire-0.6.3-windows-x64.zip.sha256).Split(" ")[0]
    → True
  2. Install: Expand-Archive .\ripwire-0.6.3-windows-x64.zip "$env:LOCALAPPDATA\Programs" and then
    $env:Path = "$env:LOCALAPPDATA\Programs\ripwire-0.6.3-windows-x64;$env:Path"
    → no error. (The README's Windows section has the line that makes it permanent.)
  3. Run: ripwire --version
    → ripwire 0.6.3 (Release, Clang …, emit=std::print, built_from=…). Did SmartScreen or your antivirus say anything? (It needs an AVX2 CPU, 2013 or later; an older one fails right here.)
  4. Map a repo you work on: cd <your repo>; Measure-Command { cmd /c "ripwire . > a.xml" } and then
    Measure-Command { cmd /c "ripwire . > b.xml" }; fc.exe /b a.xml b.xml
    (on Windows PowerShell 5.1, a bare ripwire . > a.xml re-encodes the redirect to UTF-16 with CRLF; routing it
    through cmd /c keeps the program's own bytes)
    → XML in a.xml, the second run faster (it hits the cache), and FC: no differences encountered.
  5. Doctor: ripwire . --doctor
    → every <c … ok="1">, except binary-path, which is marked degraded="1" on Windows (a known gap). The
    cache-dir row's dir= should be under AppData/Local/Temp/ripwire-….
  6. Real questions: ripwire . --for="<something you're actually working on>" and
    ripwire . --callers=<a function you know well>
    → do the answers look right for your code? Paths with /, nothing missing that you'd expect?
  7. Your agent (optional): claude mcp add ripwire -- "$env:LOCALAPPDATA\Programs\ripwire-0.6.3-windows-x64\ripwire.exe" --mcp
    (step 2's $env:Path change only lasts this PowerShell window, so the agent process your terminal launches may
    not see ripwire on its own PATH — the full path always works), or from Git Bash in the unzipped folder
    bash skills/install.sh (Claude Code) or bash skills/install.sh --codex (Codex)
    → the MCP server shows as connected, or the installer ends with done. 16 ripwire skills active ….

Especially useful: Windows on ARM (Snapdragon; it runs under x64 emulation and needs AVX2 there), a machine
without Git for Windows, Windows PowerShell 5.1, and Windows 11 with Smart App Control on (it can block unsigned
exes outright, not just warn).

How to report back: reply here with your Windows version (winver), your CPU, the ripwire --version line,
and for each step either "ok" or what you saw (paste the output, or attach a.xml / the doctor output). If something
fails, a new issue with the same details is great too. "It all worked" is just as useful as a bug.

Thank you. Your earlier Windows reports (#44, #326) are what made this possible.

Dominant language
C++
Stars
2.3k
Forks
145
Avg merge
8h 50m
Merged PRs (30d)
211

Getting set up

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 redhat-et/ripwire

All issues in redhat-et/ripwire

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.