[jeferson0306]

go get github.com/jeferson0306/api-data-validator/validate

result := validate.CPF("529.982.247-25")
result.Valid      // true
result.Normalized // "52998224725"

The logic was trapped inside an HTTP service. Nobody could go get it, the module path (DataValidatorAPI) was not even a valid import path, and importing the package would have opened a Redis connection.

What makes it a library

The library is pure. No network, no cache, no configuration, no state, nothing read from the environment. Validation is arithmetic, and arithmetic that needs a server is arithmetic you cannot trust when the server is down.

The Redis client left the library for internal/cache. It was a package-level variable, so importing a CPF validator dialled a database — the single clearest sign this was not a library.

Functions return a Result rather than three unnamed values. (bool, string, string) is fine inside a package and hostile across one.

The package is named for what it provides. validate.CPF reads better than utils.ValidateCPF, and Go style avoids the stutter.

The benchmarks change an argument

BenchmarkCPF-12                  522 ns/op
BenchmarkCNPJ-12                 499 ns/op
BenchmarkBoleto-12               864 ns/op
BenchmarkStateRegistration-12    248 ns/op

A CPF check costs 522 nanoseconds. The Redis round trip measured in production was 150–220 milliseconds — five orders of magnitude apart. Worse, building the cache key requires the normalised value, and normalising is most of the validation, so the answer is already computed before the cache is consulted.

The cache is retained because from_cache is part of the published response, but the numbers argue for removing both. Your call — I did not want to drop a published field without asking.

This is also a production fix. The cache is now opt-in through REDIS_ADDR. With none configured — the current state on Render — the service was attempting a connection and timing out on every CPF request. It now skips it. /health gained a third state to say so:

{"cache":"disabled","status":"ok"}

Command line

go install github.com/jeferson0306/api-data-validator/cmd/brdoc@latest

brdoc cpf 529.982.247-25 && echo accepted
brdoc ie 0100482300112 AC
brdoc --json cnpj 33.000.167/0001-01 | jq .normalized

Exit 0 for valid, 1 for invalid, 2 for usage — so it composes with a shell rather than needing to be parsed.

Documentation

Seven runnable examples, which are both the documentation on pkg.go.dev and tests that fail if the behaviour drifts. They cover the things worth knowing before using it: that stray characters are rejected rather than stripped, that a rejected value comes back untouched, and that ie needs its state.

The deployment is untouched

main.go stays at the repository root, so the existing Render build command still finds it. Smoke tested end to end against a running binary: every endpoint answers correctly, the batch works, and the log still contains no trace of the value being validated.

Follow-ups

The repository is named api-data-validator, which makes the import path read oddly for a library. Renaming it — GitHub redirects the old URL — would give github.com/jeferson0306/brdoc/validate. Worth doing before anyone depends on the current path, but it is a decision, not a cleanup.