Modguard – a lightweight Python tool for enforcing modular design

In plain words

Modguard is a lightweight Python tool that enforces modular, decoupled package architecture to prevent code sprawl and tightly coupled imports. It helps development teams maintain independent domains and avoid "balls of mud" that become difficult to test and modify. The tool addresses issues like unintended private module access that can degrade performance and create security problems, making codebases easier to manage as they grow.

written from the facts on this page · September 2026

From the sources

A Python tool to visualize + enforce dependencies, using modular architecture 🌎 Open source 🐍 Installable via pip 🔧 Able to be adopted incrementally - ⚡ Implemented with no runtime impact ♾️ Interoperable with your existing systems 🦀 Written in rust - tach-org/tach

In the maker’s words, at launch

Hi HN! We are excited to show you modguard - a Python tool we built to enforce a modular, decoupled package architecture. We built modguard to solve a recurring problem that we've experienced on software teams - code sprawl. Over time, cross-module imports would tightly couple together what used to be independent…

• 
  Modguard2024 · github.com · ▲6

  A lightweight python tool for enforcing modular design

• 
  Modshim – A new alternative to monkey-patching in Python2025 · github.com · ▲109

  I've invented a new alternative to forking / vendoring / monkey-patching packages in Python. It's a bit like OverlayFS for Python modules - it allows you write modifications for a target module (lower) in a new module (upper), and have these combined in a new virtual module (mount). It works by rewriting imports using AST transformations, then running both the lower and upper module's code in the new Python module. This prevents polluting the global namespace when monkey-patching, and means if you want to make changes to a third-party package, you don't have to take on the…

• 
  Artifact Keeper – Open-Source Artifactory/Nexus Alternative in RustFeb 2026 · github.com · ▲166

  I'm a software engineer who keeps getting pulled into DevOps no matter how hard I try to escape it. I recently moved into a Lead DevOps Engineer role writing tooling to automate a lot of the pain away. On my own time outside of work, I built Artifact Keeper — a self-hosted artifact registry that supports 45+ package formats. Security scanning, SSO, replication, WASM plugins — it's all in the MIT-licensed release. No enterprise tier. No feature gates. No surprise invoices. Your package managers — pip, npm, docker, cargo, helm, go, all of them — talk directly to it using their native…

• 
  A simple, highly commented, rootkit which attacks GCC and Python2014 · github.com · ▲94
• 
  DepsGuard – One command to harden NPM/pnpm/yarn/bun/uv configsJun 2026 · github.com · ▲40

  I kept seeing every npm/pnpm/yarn/bun/uv supply chain post end with the same advice (set a minimum release age, turn off install scripts), and while I know cooldowns are "controversial", they do work. But even if you convince people that they should set cooldowns, it seems many don't end up following through, not sure why, maybe because it means hand-editing five config files in five formats with five different time units, or perhaps the "it won't happen to me" syndrome (or "I'll do it later, it seems complicated" where it's actually very simple). So I created a tool that…

• 
  Sandboxing untrusted code using WebAssemblyFeb 2026 · github.com · ▲76

  Hi everyone, I built a runtime to isolate untrusted code using wasm sandboxes. Basically, it protects your host system from problems that untrusted code can cause. We’ve had a great discussion about sandboxing in Python lately that elaborates a bit more on the problem [1]. In TypeScript, wasm integration is even more natural thanks to the close proximity between both ecosystems. The core is built in Rust. On top of that, I use WASI 0.2 via wasmtime and the component model, along with custom SDKs that keep things as idiomatic as possible. For example, in Python we have a simple decorator:…

• 
  /dev/null▲482

  a social network for devs

  Dev tools · 3d ago · dev-null.sh

• 
  Whiteboard (YC W26) – an open-source IDE for thoughtful software design▲423

  open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.

  Dev tools · 28d ago · github.com

• 
  Reladraw – A diagram language where you decide where to place things▲411

  Contribute to reladraw/reladraw development by creating an account on GitHub.

  Dev tools · 26d ago · github.com

• 
  OpenBot▲362

  Grok Bot alternative: free, local, open-source, multiplayer

  Dev tools · 23d ago · openbot.run

• 
  Talanoa▲346

  Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…

  Dev tools · 20d ago · talanoa.email

• 
  CoreSpeed▲332

  One MCP for everything your agents need: apps, memory, tools

  Dev tools · 28d ago · corespeed.io

• 
  Flipner AI▲1,623

  Capture your ideas & craft texts with AI's touch

  AI · 2024 · flipner.webflow.io

• 
  Typeframes▲1,315

  Video creation for makers

  Work · 2024 · revid.ai

• 
  Superlist▲1,252

  The task layer for your AI agents

  Work · 2024 · superlist.com

• 
  MarketingIdeas.com▲1,230

  Never run out of marketing ideas ever again

  Growth · 2024 · marketingideas.com

• 
  Layers▲1,198

  A home for designers

  Work · 2024 · layers.to

• 
  Heyday▲1,178

  AI copilot for your own research, notes & conversations

  AI · 2024 · heyday.xyz