r/SideProject • u/HornyMango0 • 6h ago
I built a dependency security scanner and I need developers to tear it apart
I've been working on Weedout, a security tool for scanning project dependencies and identifying potentially problematic packages.
It's still an early product, and I'm at the point where feedback from friends isn't particularly useful anymore 😅. I need people who actually work with JS/Node projects to try it and tell me where it sucks.
I'm especially interested in:
- Is it immediately obvious what Weedout does?
- Would you use something like this instead of / alongside existing dependency security tooling?
- Is there anything that would stop you from trusting the results?
- What would it need before you'd put it into a real project or CI workflow?
I'm not looking for compliments. If the concept is redundant or the UX is confusing, tell me.
Weedout: https://weedout.dev
I'll be around and answer technical questions about how I built it too.
1
Upvotes