Repo brief: doitsujin/dxvk

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T19:27:03.133Z · commit adeda6639a09

Verdict

Mixed — Mixed signals — read the receipts

• Last commit today
• 13 active contributors
• Zlib licensed
• CI configured

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

DXVK is a Vulkan-based translation layer that implements Direct3D 8, 9, 10, and 11 APIs on Linux via Wine, allowing Windows games and applications to run natively on Linux by converting D3D graphics calls to Vulkan commands. It bridges the gap between DirectX-only Windows software and the open-source Vulkan graphics stack, eliminating the need for software rasterization or incomplete D3D emulation. Modular monorepo organized by D3D version: src/d3d10, src/d3d11, etc., each containing API implementations (device, context, shaders, buffers, textures, samplers, views). Core patterns: device objects (d3d10_device.cpp/.h, d3d11_context.cpp/.h), command buffering (d3d11_cmdlist.cpp), state…

Start here

Open these first:

• src/d3d11/d3d11_device.cpp — Core D3D11 device implementation that manages GPU resources and serves as primary entry point for Direct3D applications.
• src/d3d11/d3d11_context.cpp — Immediate context implementation handling command recording and execution, critical for render pipeline flow.
• src/d3d11/d3d11_shader.cpp — Shader compilation and management layer translating HLSL to Vulkan SPIR-V bytecode.
• src/d3d10/d3d10_device.cpp — D3D10 device implementation providing legacy API compatibility layer over shared Vulkan translation infrastructure.
• src/d3d11/d3d11_swapchain.cpp — Swap chain management coordinating presentation and frame synchronization between Wine and Vulkan.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Repository data does not include package manifests (package.json, setup.py, CMakeLists.txt, etc.) needed to infer conventional setup commands. The meson.build files indicate Meson is the build system. Before attempting…

Daily commands:

Not specified in repository data. Build likely requires: meson setup builddir && ninja -C builddir (standard Meson workflow), but this should be verified against the full repository's build documentation. Runtime requ…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 73% of recent commits
• Non-standard license (Zlib) — review terms
• No tests detected in the complete Git tree
• No environment variables, build manifests, or CI configuration visible in the supplied data—verify repository documentation before attempting builds. DLL placement is version-sensitive (64-bit vs. 32-bit prefix layouts…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.