t3-oss/t3-env

t3-env is a TypeScript package that validates environment variables at runtime and compile time using schema validation.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 9 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on April 23rd, 2023
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 128
Total Stargazers: 4,005 (+0)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.3 days
Mean response time: 41.7 days
90th percentile: 119.6 days
Tracked items: 71

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 645 days
Stale 30+ days: 18
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • PRs Accepted (7)
  • bug (2)
  • bug - p0 (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

t3-env is a TypeScript package that validates environment variables at runtime and compile time using schema validation.

The problem it solves is preventing deployments with invalid or missing environment variables. It works by letting you define a schema for your environment variables using any Standard Schema compliant validator such as Zod or Valibot, then checking that actual environment variables match that schema. The package supports the full power of these validators, including transforms and default values, and provides autocompletion and type inference when you use the schema in your application.

You should choose this tool if you want type-safe environment variable handling with validation that catches configuration errors before deployment. It suits any TypeScript project that needs to ensure environment variables are present and correctly typed. The package is ESM only and requires a TypeScript configuration with appropriate module resolution settings.

The project typically responds to issues and pull requests within one to two weeks. Work in the issue tracker centers on pull requests, bug reports, and questions from users.