In this episode, I talk about how during the past couple of days I have been working on adding a netlfiy-cms to my Gatsby site. Not that I want it for myself necessarily, although it is great to have an alternative when wanted or needed, but I want to make blogging life as easy as possible for my clients. However, there have been a few bumps along the way due to certain incompatibilities which had to be fixed.
I have spoken or written about this topic before, but feel the need to re-address it.
Node Security/npm audit appeared for the first time in my Terminal window in March of last year (2018). I had read that it was a new feature in npm created by Node Security, and was excited about the prospect of knowing more about what was going on under the hood with my npm packages and how that all boded for Web/Software Development and Individual Machine(s) Security. Previously, many of us were under the false impression that everything in our code, in our workflows using third party plugins and packages passed muster.
Correction to podcast (also added to transcript on interglobalmedianetwork.com website):
If, when you clone or download something from a repository, and then run npm i (assuming there is a package.json present), and there is a message (correction: npmjs and not Node Security) stating that it has detected vulnerabilities in your package(s), follow their instructions to run npm audit.
In this episode, I talk about Washington Post columnist Geoffrey A. Fowler's article entitled "Review: Google Chrome has become surveillance software. It’s time to switch.", but does Firefox stand up against it?
In this episode, I talk about the second patch that was made to Firefox this week to fix a second vulnerability in the browser software and how important it is to keep abreast of cyber security news and what is going on around us and the tools we use every day.