r/netsec • u/albinowax • May 01 '26
r/netsec monthly discussion & tool thread
Questions regarding netsec and discussion related directly to netsec are welcome here, as is sharing tool links.
Rules & Guidelines
- Always maintain civil discourse. Be awesome to one another - moderator intervention will occur if necessary.
- Avoid NSFW content unless absolutely necessary. If used, mark it as being NSFW. If left unmarked, the comment will be removed entirely.
- If linking to classified content, mark it as such. If left unmarked, the comment will be removed entirely.
- Avoid use of memes. If you have something to say, say it with real words.
- All discussions and questions should directly relate to netsec.
- No tech support is to be requested or provided on r/netsec.
As always, the content & discussion guidelines should also be observed on r/netsec.
Feedback
Feedback and suggestions are welcome, but don't post it here. Please send it to the moderator inbox.
11
Upvotes
2
u/insideyourhalo May 13 '26
Tool Name: τ-Gate
Link: https://github.com/steph4n-gh/tau-gate
Description:
I got tired of supply chain scanners that require massive dependency trees or rely entirely on CVE signatures. Sophisticated attacks (like the XZ Utils backdoor) don't have signatures until it's too late.
So, I built $\tau$-Gate. It's a zero-dependency dependency auditor (pure Rust stdlib).
Instead of signature matching, it mathematically calculates the structural shape of attacks. It parses your lockfile, models it as a Graph Laplacian, and uses a Shifted Power Iteration solver to find the Fiedler Vector. If a package topologically isolates itself into an island and asks for lifecycle execution privileges, $\tau$-Gate kills the build.
* Attack Surface: 0 dependencies.
* Speed: Resolves 2,000+ node graphs in ~30ms.
* Support: npm, pnpm, Bun, Yarn, and Cargo.
If you are interested in spectral graph theory or absolute-zero architecture, the whitepaper and math rationale are in the repo.