govalidStruct validation that just works.

Composable, i18n-ready, panic-safe — declared with struct tags, extended with your own checkers.

Get Started

Checkers Reference

View on GitHub

🏷️

Tag-based, no setup

Declare validation rules right next to your struct fields. No builders, no schema files — your struct is the schema.

🧱

Composable

Chain multiple checkers per field with a single semicolon. Mix built-in rules and your own to model real-world constraints.

🌐

Internationalized

Chinese and English ship out of the box. Plug in any locale, override any message, or attach per-field labels for each language.

🔌

Extensible

🛡️

Safe by default

Handles nil pointers, maps, channels, embedded fields and unexported fields without panicking — fuzz-tested across millions of inputs.

⚡

Tiny & fast

Pure-reflection core, ~1.6µs to validate a typical struct. No code generation, no third-party dependencies beyond x/text.

A familiar Go API

package main

import (
    "fmt"

    "github.com/wuhan005/govalid"
)

func main() {
    v := struct {
        Name string `valid:"required;username" label:"昵称"`
        ID   int    `valid:"required;min:0;max:999" label:"用户编号"`
        Mail string `valid:"required;email"     label:"邮箱"`
    }{
        Name: "e99_",
        ID:   1990,
        Mail: "i@github.red.",
    }

    if errs, ok := govalid.Check(v); !ok {
        for _, err := range errs {
            fmt.Println(err)
        }
    }
}

text

昵称的最后一个字符不能为下划线
用户编号应小于999
邮箱不是合法的电子邮箱格式

Why govalid?

	govalid	Bring-your-own `if`
Where rules live	Beside the field, in struct tags	Scattered across handlers
Cross-field rules	`equal:` checker + `Validate()`	Manual conditionals
Localized messages	Built-in i18n + `SetMessageTemplates`	DIY
Custom rules	`Checkers["myRule"] = …`	Copy-paste functions
Safety on weird inputs	nil/map/embedded/unexported handled	Up to you