internal/worker: initialize non-modules in govulncheck pipeline

Similar to analysis pipeline, we go mod init and go mod tidy a project
that is not a module.

The rationale is that although these projects are not modules, they can
still be used as a dependency by other projects. When that happens, the
dependencies of the non-module project are fetched at their latest
version, which is exactly what the initialization will do anyhow.

Change-Id: Ib111dca52873aaaf0f0d7d6510a083cfbf22f96d
Run-TryBot: Zvonimir Pavlinovic <>
TryBot-Result: Gopher Robot <>
Reviewed-by: Maceo Thompson <>
1 file changed
tree: 72496c7aab1ab50a044f74644ff7f1f372d283ca
  1. cmd/
  2. deploy/
  3. devtools/
  4. internal/
  5. terraform/
  6. .dockerignore
  7. .gitignore
  8. all_test.go
  9. checks.bash
  10. config.json.commented
  12. go.mod
  13. go.sum
  15. Makefile
  18. tools.go


This repository contains code that serves

Report Issues / Send Patches

This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see

The main issue tracker for the time repository is located at Prefix your issue with “x/pkgsite-metrics:” in the subject line, so it is easy to find.