

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Still calibrating
click for more info
Not enough gems
Cost: 6 gems
1: Managing Secrets
incomplete
2: Injecting Secrets at Runtime
incomplete
3: Protecting Secrets
incomplete
4: Build Artifacts and Deployment Hygiene
incomplete
5: Limiting Build Context
incomplete
6: Source Code and Config Leaks
incomplete
7: Public File Leaks
incomplete
8: Server-Side Request Forgery
incomplete
9: Defending Against SSRF
incomplete
10: Open Redirects
incomplete
11: Risks of Dependencies
incomplete
12: Auditing Dependencies
incomplete
13: Dependency Maintenance
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Go provides separate checks for module integrity, module hygiene, and known vulnerabilities.
go mod verify
go mod tidy -diff
go run golang.org/x/vuln/cmd/[email protected] ./...
go mod verify checks that downloaded module content still matches its recorded hashes. go mod tidy -diff reports whether the module files need changes without rewriting them. govulncheck compares the application's reachable code with published Go vulnerability data.
A clean report is useful, but it is not proof that the dependencies are safe. An unpublished vulnerability, malicious behavior without an advisory, or risky application code will not appear merely because the module graph verifies.
When a scan reports a reachable vulnerability, inspect the affected call path, fixed version, and compatibility impact before updating.
Verify Bearly Secure's module graph and audit its reachable dependencies without changing the project.
go run golang.org/x/vuln/cmd/[email protected] ./...
Run and submit the CLI tests from the project root.