Privacy choices
Git-Stars uses essential storage for site operation. Optional analytics stays disabled unless you accept it. This choice does not enable advertising. Privacy Policy
Check specific documented prerequisites and see exactly what remains unverified.
Reference version: 0.1.8 · Not a latest-release recommendation
Answer the questions to begin. Unanswered conditions never count as met.
This profile checks the declared Python range only. Select format extras separately; OCR, codecs, OS-specific dependencies, isolation and memory for your files remain unverified. A Python match is not an installation or file-conversion test.
A match is not evidence of successful installation, sufficient hardware, a secure release or production readiness.
2026-10-16 · 0.1.8
Select a documented installation method and match the reference version before answering. This first edition covers the declared Python range for MarkItDown 0.1.8, Docker plus persistent storage for a Qdrant 1.15.5 local trial, and Python/uv for Langflow 1.6.5. The narrow checks are deliberate: unsupported hardware figures are not inferred. Historical profiles help inspect an existing setup, not select a secure current release.
If your Langflow 1.6.5 environment has Python 3.14, the version check is missing even if uv is installed: that release declares Python below 3.14. Leave Python unanswered and it becomes unknown, not missing or passed. Changing the target release clears the old result. Before installing any historical version, review its current advisories and supported upgrade path.
This is a prerequisite worksheet, not an environment scanner. It cannot inspect OS build tools, reserve ports, verify free memory, check a model API account or run a container. A matching result covers only the listed conditions. Memory and GPU needs depend on the chosen pipeline and workload; no unsupported minimum is supplied. Pin the intended version and verify its own documentation. Source checks: October 16, 2026.
Git-Stars Editorial · Independent tools; not affiliated with the projects mentioned. Editorial policy