# missing go.sum entry for module providing package How to fix it.

URL: https://antideploy.com/blog/go-missing-go-sum-entry

Your go.sum file is missing an entry. Run go mod tidy on your machine and commit go.mod and go.sum.

**What you see**

```
go: github.com/gin-gonic/gin@v1.9.1: missing go.sum entry for go.mod file
main.go:5:2: missing go.sum entry for module providing package
github.com/gin-gonic/gin
```

## At a glance

- **What it means**: go.sum is incomplete
- **The fix**: Run go mod tidy
- **Then**: Commit go.mod and go.sum
- **Why**: A package was added without tidy

Published 7 October 2026. Facts checked 7 October 2026. 1 min read.

## What it means

`go.mod` lists the modules your program uses. `go.sum` holds checksums for them. A package was added to your code or to `go.mod`, but its checksum was not recorded, so the build stops. The build says it in one line: `go.sum` is incomplete.

## How to fix it

### 1. Run go mod tidy on your machine

It adds the missing entries and removes the ones you no longer use.

### 2. Commit go.mod and go.sum

Both files must be sent with your code.

### 3. Deploy again

A failed deploy never counts against your plan.

## Why it happens

A coding agent adds an import, or edits `go.mod` by hand, and does not run `go mod tidy`. The program still builds on a machine whose module cache already holds the package, and fails on a clean server.

## Go module questions, answered.

Anything else? Write to us and a person answers.

[support@antideploy.com](mailto:support@antideploy.com)

### Why does it work on my machine?

Your machine may already have the module downloaded. A clean build server does not.

### Does this failed deploy cost anything?

No. Failed deploys never count against your plan.

### Should I commit go.sum?

Yes. Commit both `go.mod` and `go.sum`, so every build uses the same checksums.

## More guides, and the platform.

Each platform page covers one part of Antideploy: what it does, where it stops and the questions people ask. [See the whole platform](https://antideploy.com/platform), or [all the guides](https://antideploy.com/blog).

- [How to deploy a Go app](https://antideploy.com/blog/how-to-deploy-a-go-app): go.mod, the built binary, the PORT variable, Postgres and the go.sum fix.
- [Your app built successfully but never started listening on its port](https://antideploy.com/blog/your-app-built-successfully-but-never-started-listening-on-its-port): The app built but never answered on its port. Read PORT, listen on 0.0.0.0 and check the logs.
- [npm ci can only install packages when your package.json and package-lock.json are in sync](https://antideploy.com/blog/npm-ci-can-only-install-packages-when-package-json-and-package-lock-json-are-in-sync): The lock file does not match package.json. Run npm install and commit the lock file.

- [Deployments](https://antideploy.com/platform/deployments)
- [Logs and monitoring](https://antideploy.com/platform/logs-and-monitoring)

Facts on this page were checked against the live platform on 7 October 2026.

## Deploy something. Start with one sentence.

Paste one sentence into your coding agent, click Approve once, and get a live link. No card, no trial clock.

To set this up, give your coding agent this sentence:

```text
Set this project up to deploy on Antideploy. Fetch https://antideploy.com/agent.md and follow it.
```