cpan-audit VS app-bmt

/u/briandfoy also says: "We've revitalized CPAN::Audit. It's a tool that can scan your installed modules for known security issues. It's all at cpan-audit. Along with that, I'm soliciting people to sign the keys that I use to sign the data that we distribute. Since this is security software, we want people to trust the data that we are giving them. Just follow the instructions."

When I build my tools, I make them external to the files I want to create. I still want to make my distributions look mostly that same so it's easier to work on them in bulk, and I do that mostly in the same way. You just won't find tool-specific commands inside the files. I have this thing I call bmt, which you shouldn't use because I'm not going to commit to supporting you using it, especially in a way I don't want to use it. But it's out there. I do the same things in the same way in most of my repos, but I'm just approaching it differently.