Audit before master goes live
See original GitHub issueFollowing on from the discussion in https://github.com/freeCodeCamp/freeCodeCamp/pull/36522 this is just a reminder that npm audit needs running on all the packages (api-server, client etc.) before master goes live.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Auditing 101 | Part 1: Starting the Audit - YouTube
Check out a FREE PREVIEW of My Comprehensive Audit Course: https://courses.maxwellcpareview.com/courses/comprehensiveauditexamcourseI'm here ...
Read more >What Degree Do People With a Job in Auditing Have?
Therefore, as indicated by the ACFE, the path to becoming an internal auditor is with a bachelor's or master's degree plus certifications.
Read more >Internal Audit Checklist: Order Processing - Vonya Global
When conducting an audit of order processing, consider this Internal Audit checklist as a way to ensure that orders are registered accurately.
Read more >Best Time to Leave Big 4 Audit Experience | Wall Street Oasis
I'm finishing up my first year as an audit senior and going through the 'should I stay (until manager) or should I go'...
Read more >Auditing in a computer-based environment - ACCA Global
Application controls, comprising input, processing, output and master file ... should be designed and then tested prior to 'live' running with real data....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Anything that’s dev only (which those seem to be) is not too worrying. If there are production packages with security problems, then they usually need addressing, though.
The ones you’ve shown shouldn’t be a problem, but updating and fixing things is a good idea in general, so please do.
By the way, if you do find any security issues please don’t discuss it here. Please email
security@freecodecamp.orginstead.I would hang on to this. I have an upcoming PR #38241 which should resolve most things.