---
title: "testcontainers-go"
pageType: "tool-profile"
schemaVersion: "1.0"
snapshotId: "tv-20260915-f4c107995a2e"
generatedAt: "2026-09-15T07:02:20.000Z"
canonicalUrl: "https://toolvitals.com/tools/testcontainers-go/"
jsonUrl: "https://toolvitals.com/api/agent/tools/testcontainers-go"
indexable: true
---

# testcontainers-go

Testcontainers for Go is a Go package that makes it simple to create and clean up container-based dependencies for automated integration/smoke tests. The clean, easy-to-use API enables developers to programmatically defi

## Decision context

- Status: active
- ToolVitals score: 94/100
- Health score: 95/100
- Shipping score: 93/100
- Score mode: verdict
- Data confidence: 90/100
- Source coverage: 85/100
- Last evidence check: 2026-09-14

## Classification

- Use case: API Development & Testing (api-development-testing)
- Category: Developer Tools (developer-tools)
- Tool mode: Source-visible project
- Openness: OSI-approved OSS
- License: MIT
- Tags: automation, workflow, open-source, api-first, docker, go, golang, hacktoberfest, testcontainers, testcontainers-go, testing, integration-testing, smoke-testing, containerized-testing

## Public repository signals

- Repository: [testcontainers/testcontainers-go](https://github.com/testcontainers/testcontainers-go)
- Stars: 4974 (adoption context only)
- Forks: 636
- Open issues: 175
- Last commit date: 2026-09-11
- Releases in 90 days: 2

## Source receipts

- [Official website](https://golang.testcontainers.org/) — checked 2026-09-14
- [Source repository](https://github.com/testcontainers/testcontainers-go) — checked 2026-09-14

## Discovery status

- Search indexable: yes
- Reason: sufficient tool evidence

## Interpretation limits

- ToolVitals scores summarize bounded public maintenance, shipping, openness, and evidence signals. They are not user-review ratings.
- GitHub stars and related popularity metrics are adoption context, not quality evidence.
- Missing values mean not collected or not confidently established; they do not mean zero.
- Public signals do not prove security, uptime, support quality, customer satisfaction, or production suitability.
- Verify material decisions against the linked first-party sources and your own requirements.