Maker builds $96 3D-printed guided rocket, GitHub project draws security scrutiny

A $96 open-source rocket prototype posted by engineer Alisher Khojayev spread fast enough on GitHub to turn a maker project into a moderation headache. The repository, MANPADS-System-Launcher-and-Rocket, had climbed to roughly 2.4k stars and 677 forks, a signal that the files were not just being admired but actively copied, studied, and circulated.

The README frames the project as a proof-of-concept for a low-cost rocket launcher and guided rocket system built with consumer electronics and 3D-printed components. The design pairs folding fins with canard stabilization, while an onboard ESP32 flight computer and MPU6050 inertial measurement unit handle guidance. The launcher also folds in GPS, compass, and barometric sensors for orientation and telemetry, a parts list that shows how far hobbyist hardware has moved beyond simple radio control and into software-defined control loops.

Khojayev built the project in Fusion 360 and simulated it in OpenRocket, then packaged the repository with CAD files, firmware, simulation files, documentation, and a linked Google Drive archive. That archive adds development media, system flow diagrams, rocket specifications, a bill of materials, and cost breakdowns, making the project feel less like a one-off stunt and more like a reproducible package. For platform moderators, that is exactly where the concern starts: once a weapons-adjacent concept arrives with documentation, simulation data, and firmware, the line between demonstration and dissemination gets thinner.

Security officials and analysts have taken the project as a warning about how cheaply guided weapons-like systems can be assembled from consumer parts. Some coverage compared the prototype’s $96 price tag with the far higher cost of the U.S. military’s Stinger missile system, underscoring the asymmetry between a garage-scale build and established defense hardware. The prototype’s real-world operational performance remains unverified, but the online reaction has already shifted the story from novelty to policy problem.

That shift matters far beyond one GitHub repo. Maker communities have long debated where experimentation ends and reckless publication begins, and printable weapons files now sit squarely in that argument. GitHub’s challenge is no longer just hosting code; it is deciding how to handle repositories that bundle CAD, firmware, and build media into a shared path toward hardware with obvious abuse potential.