I definitely want to give proper credit to the work you’ve put into ArchCanary. I know these detection rules and the layered approach take a lot of thought and effort, so I don’t want that work to go unnoticed.
I’ll make sure the relevant rules are properly attributed and licensed in NeoArch. I’d also be happy to include ArchCanary in NeoArch’s community/plugin ecosystem and add it to the project’s supported security resources, with a link back to your project and README. That way, people who find these protections through NeoArch can also discover the original work.
I really appreciate you being open to this. Open source really is great when projects can build on each other like this.
I’ve installed NeoArch from AUR using Pacseek. . . I like the immediate responsiveness taking the guess work out of performative functions. I’ll willing to give devlopers the chance to articulate concepts for the user willing to give their work a try. NeoArch and Archcanary are both installed I my machine. It’s worth the time to see if they come to fruition for many people. Computers and software are like what ‘ham’ and radio were once to hobbyists. Maybe ‘AI’ will be the end of personal computing. . .
Thanks, Rich! I really appreciate you taking the time to actually install and try NeoArch, especially through Pacseek. That means a lot.
I’m glad you like the responsiveness. One thing I care about with NeoArch is making system operations clear and responsive instead of leaving the user guessing about what is happening.
And regarding Pacseek, I actually think it is a great tool. Personally, I don’t want NeoArch to become another CLI replacement or try to compete with Pacseek in that area. Pacseek already does that job very well. My focus with NeoArch is more on bringing the different package and system-management functions together in one GUI, while still providing a CLI for people who want it.
Also, I agree that developers should have the opportunity to explain their ideas and let users actually try the software before judging it. I have nothing against using AI during development either. I use AI myself as a kind of pair programmer — for example, to help investigate bugs, think through an implementation, or review an approach. But I personally don’t recommend blindly “vibe coding” an entire project without understanding and reviewing what is being produced.
For me, there is a big difference between using AI to help you develop a project and letting AI generate a project that you don’t really understand. The second approach can easily leave behind dead code, unnecessary complexity, or security vulnerabilities. I still want to understand the code, test it, and take responsibility for what goes into NeoArch.
I’m continuing to work on it and hopefully it can become genuinely useful to more people over time. Thanks again for giving both NeoArch and ArchCanary a chance!
