Should you use it?
Consider Holo Card Studio when the deliverable needs both a browser card and a Blender scene you can edit. Budget time to inspect the artwork, render the saved scene, and check the viewer. Our run does not support treating the workflow as proven unattended production tooling.
The English README documents two routes. Holographic cards combine background, subject, line-art, and text layers. Lenticular cards switch between two complete artworks as the viewing angle changes. The documented outputs include an editable Blender project and a Three.js viewer. These are documented capabilities, not outputs we verified in our sandbox.
What our sandbox established
Our run took place on September 29, 2026, at commit cce9718 (full SHA cce97187874f8aac53ab8374ed1d4decaa6c0116). The stored sandbox record identifies a Python 3.12 container with 3 CPUs and 8 GB of memory. No new execution was performed for this correction.
The harness records command outcomes as success or failure, exit codes, elapsed time, and parsed test counts. Installation returned exit code 0 in 22 seconds; the build step returned exit code 0 in 10 seconds. The record reports 35 installed packages occupying 37 MB. The build log tail is empty, so its successful status supplies no evidence that Blender rendered a card or that a viewer was opened.
The test step returned exit code 1 after 12 seconds. Its stored parser summary records 6 passed, 1 failed, and 7 total, with no skipped tests or errors. These stored parser summaries do not establish exhaustive unique test coverage. Separately, the raw suite footer reports "1 failed, 6 passed, 3 subtests passed in 0.31s". The subtests are not added to the stored aggregate, and the footer's duration is distinct from the harness's elapsed test-step time.
The raw failure was ModuleNotFoundError: No module named 'PIL'. It occurred in HolographicFailureTests.test_failed_blender_stops_even_when_old_outputs_exist, at the import before the intended failure-handling check. This shows that Pillow was unavailable to that test process. It does not establish a Blender defect, a pipeline defect, or the cause of the environment mismatch. The README explicitly requires Python 3 plus Pillow.
The audit record reports zero pip-audit advisories. Scan coverage is unknown: the record supplies no scannedPackages value, and its packages field is 0. This is not evidence that all installed dependencies were scanned or that the project is secure.
The supplied MrKeyoor testing methodology explains how command outcomes and parsed counts reach a review. That page was retrieved after this run; it does not establish which methodology version governed the September execution.
What still needs checking
The verification guide requires separate checks for each route. It warns that old output files do not prove a new build succeeded and that source compatibility branches do not substitute for testing the Blender version actually used.
Our record does not establish successful Blender rendering, visual asset registration, a complete lenticular A/B transition, browser interactions, or touch-device behavior. It also does not independently establish the previously asserted Blender 5.2.2 blocker: no fetched issue extract supports that assertion here.
For a trial, first make Pillow available to the Python environment running the focused checks. Then follow the verification guide for your chosen route: inspect newly generated files and Blender logs, open or render the saved scene, and test the viewer in a real browser. Check touch on an actual touch device before claiming touch verification. The guide explicitly says its focused source checks do not replace rendering and browser inspection.
The browser and Blender outputs also need separate visual judgment. The README says their lighting, colors, glow, and back artwork are not identical. Matching effects does not mean matching pixels.
Alternatives and their roles
Blender is a free and open source 3D creation suite. It is already part of Holo Card Studio's documented workflow, so it is a complement when editing the generated scene. Choose direct Blender authoring instead when you want to build the scene yourself; that choice leaves you responsible for any browser deliverable.
Three.js is a JavaScript 3D library. It is also part of the documented workflow. Choose direct Three.js development when your task is a custom browser viewer and you can build that application yourself. Its library role does not establish a replacement for the complete card-generation workflow.
How the ratings work
These are editorial assessments, not benchmark results. The rubric is 1 for substantial documented obstacles, 2 for unresolved validation limits, 3 for usable foundations with material checks remaining, 4 for detailed guidance covering the task and its limits, and 5 for strong evidence across the assessed dimension. A dimension without sufficient evidence remains unassessed.
Setup ease scores 3 because installation and build returned zero, while testing encountered an unavailable dependency and output validation remains undone. Documentation scores 4 because the English README and verification guide explain requirements, both routes, and concrete acceptance checks. Maturity scores 2 because our evidence leaves end-to-end operation unverified, and the stored repository scan found no CI workflow or Dockerfile. Community is unassessed because the supplied primary extracts do not establish maintainer responsiveness or contributor support.

