How a JavaScript and TypeScript install actually behaves, and what that behaviour means for security in a large estate. Covers the path from a range in a manifest to bytes on disk, the package manager differences that change your exposure rather than your ergonomics, what a lockfile does and does not assert, why deleting a lockfile to fix a build is an unreviewed change to every dependency in the project, what an integrity hash proves and what it leaves open, lifecycle scripts and how to disable them without the breakage that makes teams revert, workspaces and the shared install graph, hoisting and the phantom dependency problem, peer dependencies and the upgrades they block, the transitive explosion that makes review at merge time impractical, overrides for forcing a transitive fix you do not own, scoped packages and the public namespace, the development dependencies that reach production anyway, a staged upgrade for a library several major versions behind, and a policy written as outcomes so it survives a change of tooling. Companion to the published Java and Python courses in the same series.
Nothing. Every course, exam, and certificate on the catalog is free — including retakes. All you need is a free Safeguard account.
None. The flagship course, Safeguard Certified Practitioner, is a beginner-level course — basic familiarity with how software is built helps, but every exam question is answerable from the lessons themselves.
You can retake it after a 24-hour cooldown, as many times as you need. Retakes are free, and each attempt draws a fresh random set of questions.
The Safeguard Certified Practitioner credential is valid for 24 months from issue. The expiry date is printed on the certificate and shown live on its public verification page. Renewing means passing the current exam again.
