I agree with @RobC here. It also disactivated running custom scripts in my package.json completely for me, which obviously is a deal breaker since you can’t define and run your custom scripts anymore.
Although it’s probably useful to think about these security concerns, I don’t think running npm config set ignore-scripts true is the right option. I ran it as well and ended up turning it back off to keep running my custom package scripts.
So the advice from the video ended up being not all too sound, I guess…