Go native fuzzing: write and run your first fuzz test
Go has fuzzing built into go test. Write a FuzzXxx function, add seeds, run with -fuzz, and keep failing inputs as regression tests. A short walkthrough.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Go has fuzzing built into go test. Write a FuzzXxx function, add seeds, run with -fuzz, and keep failing inputs as regression tests. A short walkthrough.
Go marks a deprecated module with a comment in go.mod, and go list shows it. Here is the command, what the marker covers, and how to act on it.
Vendoring copies dependencies into your repo so Go builds do not touch the network. How it works, when Go uses it automatically, and the upkeep it adds.
The go line sets a module's minimum Go version. The toolchain line suggests a toolchain, and GOTOOLCHAIN decides whether Go may download one.
The go line sets the minimum Go version a module needs. The toolchain line only suggests which toolchain to run. How both behave since Go 1.21.
To fix a vulnerable transitive Go module, require the fixed version directly. exclude only blocks a version, and replace skips authentication.
Go modules mark themselves deprecated with a comment in go.mod. Check with go list -m -u and read the message before adding or keeping a dependency.
Self service scanning means developers can run the same checks as the pipeline locally and in the IDE. Options, trade offs and a rollout plan.
Branch and merge request pipelines can both start, or neither. Use workflow rules and CI_OPEN_MERGE_REQUESTS so security jobs run once and never skip.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.