FreeCAD makes 3D edits through a model history
FreeCAD is built around parametric modeling: a dimension or earlier construction step can be changed and the later shape recalculated. Sketches provide constrained 2D geometry, which can become 3D parts and then production drawings. The README positions that workflow for product design, mechanical engineering, architecture, classrooms, and hobby projects. This breadth is useful, but it also explains why the interface is split into workbenches rather than reduced to one universal modeling screen.
The application spans several technical layers. OpenCASCADE supplies the geometry kernel, Coin3D handles the scene representation, Qt provides the interface, and Python supplies a broad scripting API. That mix gives FreeCAD more range than a simple mesh editor. It also means a contributor is entering a large native application: our checkout held 17,627 files, roughly 7,606,084 lines of source, and occupied 493.6 MB before the measured Python dependencies were installed.
The 36-package result covers Pivy, not the full application
The lab detected a Python project under src/3rdParty/pivy, FreeCAD's bundled Python binding for Coin3D. Our sandbox installed 36 packages in 34 seconds and used 37 MB for them. That is a clean result for the detected subproject, but it should not be quoted as the cost of installing the FreeCAD desktop application. The full repository is primarily C++, and the main README directs ordinary users toward precompiled releases rather than a Python package.
For source contributors, the developer handbook names CMake, Git, a code editor, a C++ compiler, and a Python interpreter. Windows uses the MSVC toolchain, macOS needs the Xcode command-line tools, and the handbook links separate platform pages for the complete dependencies. It also documents a Pixi environment as one way to manage those pieces. There are 22 CI workflow files in the checkout, but no Dockerfile that turns the native build into one standard container command.
What happened when we ran it
Our run used commit fda5c14 in an unprivileged Debian container with 3 CPUs and 8 GB of RAM. Installation finished in 34 seconds with 36 packages and 37 MB on disk. The detected Pivy build then completed successfully in 8 seconds. Pip-audit reported 0 known vulnerabilities in the installed Python packages. These measurements describe the bundled binding project, not startup speed, modeling performance, or a complete native FreeCAD build.
The test command failed with exit code 1 after 9 seconds. Pytest reported 0 passed and 0 failed because all 4 discovered modules stopped during collection or setup. The common log line was ModuleNotFoundError: No module named 'pivy.coin', reached while importing SoDB, SoNodeKit, and SoInteraction. The affected modules were two examples and two tests. The log proves the extension was unavailable in that environment; it does not show why it was unavailable.
That distinction matters when judging setup. A fresh Debian Python image was enough to install and build the detected package, yet it was not enough to begin the 4-module test set. The repository does contain a tests directory, and its 22 CI workflow files show that upstream automation exists. Neither fact turns our failed collection into a pass. A contributor should reproduce the documented platform build environment before treating Pivy's Python test command as a standalone health check.
Release 1.1.3 makes old file readers a security risk
FreeCAD 1.1.3 was published on July 25, 2026 as a maintenance release. Its release notes say several fixes address code execution and other file-handling vulnerabilities triggered by malicious FCStd files. They also state that every previously released version is affected by at least one of those issues. The practical advice is unusually direct: upgrade before opening files from unknown or untrusted sources. Signed Windows and macOS builds are listed in the same release notes.
The release also contains fixes across BIM, CAM, Sketcher, TechDraw, PartDesign, Assembly, and the application core. That spread shows both the value and the cost of FreeCAD's scope. A team may rely on only 2 workbenches while changes elsewhere still ship in the same application. For deployment in a classroom or company, pin one maintained release, test the exact workbenches and file exchange paths in use, and treat downloaded FCStd files as active input rather than harmless documents.
Same-day activity supports adoption, not effortless contribution
GitHub showed 33,087 stars, 4,115 open issues and pull requests, and a last push on August 27, 2026. Recent issue activity on that date covered Sketcher geometry, TechDraw dimensions, document recovery, CAM loading, and interface behavior. The combined count includes PRs as well as issues. Same-day push and issue updates show an active project with a large support surface. A stale tag would be a poor health signal here, and the latest release was only about 1 month old.
FreeCAD earns a serious trial because there is no subscription gate, it works across 3 desktop operating-system families, and it covers the path from constrained sketch to editable 3D model and drawing. The trial should use the current binary first. If the workbench, exchange format, and drawing output fit your job, the Python API and source access leave room to adapt it. If browser collaboration, a small codebase, or 2D-only drafting is the requirement, one of the narrower alternatives will demand less operational and training effort.