You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I'm not saying it won't. I am saying that in the grand scheme of things it's lower on my priority list of security threats. My deps are not as likely to cause security issues in a service I write. It's my own code.
If your company's net worth is in the tens or hundreds of millions and you're processing sensitive information you should absolutely be investing in auditing your dependencies. For most shops this isn't worth the time, but it's unfortunate that bigcos don't invest in it either
It's frustrating for me to see both sides of this argument, because IMO the people who don't need to care over-estimate the threat and the people who *do* need to care under-estimate it
Where I work I absolutely need to care, but in my own code outside of work 
it's about your threat model. It's highly contextual. Just for the most part it's not to me as big of an issue and tools like cargo crev are just reactionary. It doesn't solve a problem.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
