env-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Environment Variable Manager (env-manager)

环境变量管理器（env-manager）

Comprehensive environment variable validation, security scanning, and management for modern web applications.

为现代Web应用提供全面的环境变量验证、安全扫描与管理功能。

Overview

概述

The env-manager skill provides systematic environment variable management across local development, CI/CD pipelines, and deployment platforms. It prevents common issues like missing variables, exposed secrets, and framework-specific configuration errors.

Key Features:

Framework-Aware Validation: Next.js, Vite, React, Node.js, Flask support
Security-First: Never logs secrets, detects exposed credentials
Platform Integration: Ready for Vercel, Railway, Heroku, and CI/CD
Fast: Validates 1000 variables in 0.025s (80x faster than 2s target)
Zero Dependencies: Pure Python, works anywhere

env-manager工具可在本地开发、CI/CD流水线和部署平台中提供系统化的环境变量管理。它能预防缺失变量、密钥泄露、框架特定配置错误等常见问题。

核心特性：

框架感知验证：支持Next.js、Vite、React、Node.js、Flask
安全优先：绝不记录密钥，可检测暴露的凭证
平台集成：适配Vercel、Railway、Heroku及各类CI/CD系统
极速性能：0.025秒内完成1000个变量的验证（比目标速度快80倍）
零依赖：纯Python实现，可在任意环境运行

Why Use env-manager?

为什么使用env-manager？

Common problems this solves:

"Works on my machine, but not in production" (missing env vars)
Accidentally exposing API keys in client-side code (NEXT_PUBLIC_ with secrets)
Missing required variables during deployment
Inconsistent .env files across team members
No documentation of required environment variables
Security vulnerabilities from exposed secrets

它能解决的常见问题：

"在我本地能运行，但生产环境不行"（缺失环境变量）
意外在客户端代码中暴露API密钥（将密钥放在NEXT_PUBLIC_前缀变量中）
部署过程中缺失必要变量
团队成员间的.env文件不一致
没有记录必要环境变量的文档
因密钥暴露导致的安全漏洞

Quick Start

快速开始

Installation

安装

No installation needed! env-manager is a bundled skill in Claude MPM.

Requirements:

Python 3.7+
No external dependencies

无需安装！env-manager是Claude MPM中的内置工具。

系统要求：

Python 3.7+
无外部依赖

5-Minute Quick Start

5分钟快速上手

bash

undefined

bash

undefined

1. Validate your .env file

1. 验证你的.env文件

python3 scripts/validate_env.py .env

2. Check for framework-specific issues (Next.js example)

2. 检查框架特定问题（以Next.js为例）

python3 scripts/validate_env.py .env --framework nextjs

3. Compare with .env.example to find missing vars

3. 与.env.example对比，找出缺失的变量

python3 scripts/validate_env.py .env --compare-with .env.example

4. Generate .env.example for documentation

4. 生成.env.example用于文档记录

python3 scripts/validate_env.py .env --generate-example .env.example

5. Get JSON output for CI/CD integration

5. 生成JSON输出以集成到CI/CD

python3 scripts/validate_env.py .env --json


That's it! Environment variables are now validated professionally.

python3 scripts/validate_env.py .env --json


完成！现在你的环境变量已通过专业验证。

Usage Examples

使用示例

Basic Validation

基础验证

Validate a .env file for structural issues:

bash

python3 scripts/validate_env.py .env

What it checks:

Valid key=value format
No duplicate keys
Proper naming conventions (UPPERCASE_WITH_UNDERSCORES)
No empty values (unless explicitly allowed)
Proper quoting for values with spaces

Example output:

✅ Validation successful!
   - 15 variables validated
   - 0 errors
   - 0 warnings

验证.env文件的结构问题：

bash

python3 scripts/validate_env.py .env

检查内容：

有效的key=value格式
无重复键
符合命名规范（大写字母加下划线）
无空值（除非明确允许）
带空格的值需正确加引号

示例输出：

✅ 验证通过！
   - 已验证15个变量
   - 0个错误
   - 0个警告

Framework-Specific Validation

框架特定验证

Next.js

Validate Next.js environment variables:

bash

python3 scripts/validate_env.py .env.local --framework nextjs

Next.js-specific checks:

NEXT_PUBLIC_* variables are client-exposed (warns if secrets detected)
.env.local, .env.production, .env file hierarchy
Detects secrets in client-side variables

Example:

bash

undefined

验证Next.js环境变量：

bash

python3 scripts/validate_env.py .env.local --framework nextjs

Next.js专属检查：

NEXT_PUBLIC_*变量会暴露给客户端（若检测到密钥则发出警告）
.env.local、.env.production、.env的文件层级
检测客户端变量中的密钥

示例：

bash

undefined

.env.local

NEXT_PUBLIC_API_URL=https://api.example.com NEXT_PUBLIC_API_KEY=secret123 # ⚠️ WARNING: Secret in client-exposed variable! DATABASE_URL=postgresql://... # ✅ Server-side only

undefined

NEXT_PUBLIC_API_URL=https://api.example.com NEXT_PUBLIC_API_KEY=secret123 # ⚠️ 警告：客户端可访问变量中包含密钥！ DATABASE_URL=postgresql://... # ✅ 仅服务端可见

undefined

Vite

bash

python3 scripts/validate_env.py .env --framework vite

Vite-specific checks:

VITE_* variables are client-exposed
Warns if secrets detected in VITE_ prefixed vars

bash

python3 scripts/validate_env.py .env --framework vite

Vite专属检查：

VITE_*变量会暴露给客户端
若VITE_前缀变量中包含密钥则发出警告

React (Create React App)

React（Create React App）

bash

python3 scripts/validate_env.py .env --framework react

React-specific checks:

REACT_APP_* variables are client-exposed
Warns if secrets in REACT_APP_ prefixed vars

bash

python3 scripts/validate_env.py .env --framework react

React专属检查：

REACT_APP_*变量会暴露给客户端
若REACT_APP_前缀变量中包含密钥则发出警告

Node.js/Express

bash

python3 scripts/validate_env.py .env --framework nodejs

Node.js-specific checks:

Common NODE_ENV, PORT, DATABASE_URL patterns
Standard Node.js conventions

bash

python3 scripts/validate_env.py .env --framework nodejs

Node.js专属检查：

常见的NODE_ENV、PORT、DATABASE_URL格式
符合标准Node.js约定

Flask/Python

bash

python3 scripts/validate_env.py .env --framework flask

Flask-specific checks:

FLASK_APP, FLASK_ENV variables
SQLAlchemy DATABASE_URL format

bash

python3 scripts/validate_env.py .env --framework flask

Flask专属检查：

FLASK_APP、FLASK_ENV变量
SQLAlchemy DATABASE_URL格式

Comparing with .env.example

与.env.example对比

Ensure your .env has all required variables:

bash

python3 scripts/validate_env.py .env --compare-with .env.example

What it checks:

All variables in .env.example exist in .env
No extra undocumented variables in .env

Example output:

❌ Missing variables:
   - DATABASE_URL (required in .env.example)
   - STRIPE_SECRET_KEY (required in .env.example)

⚠️  Extra variables not in .env.example:
   - DEBUG_MODE (consider adding to .env.example)

Perfect for:

Onboarding new team members
CI/CD validation
Deployment pre-checks

确保你的.env包含所有必要变量：

bash

python3 scripts/validate_env.py .env --compare-with .env.example

检查内容：

.env.example中的所有变量均存在于.env中
.env中无未在.env.example中记录的额外变量

示例输出：

❌ 缺失变量：
   - DATABASE_URL（.env.example中要求必填）
   - STRIPE_SECRET_KEY（.env.example中要求必填）

⚠️  .env中存在.env.example未记录的额外变量：
   - DEBUG_MODE（建议添加到.env.example中）

适用场景：

新团队成员入职配置
CI/CD验证
部署前检查

Generating .env.example

生成.env.example

Create documentation for your environment variables:

bash

python3 scripts/validate_env.py .env --generate-example .env.example

What it does:

Reads your .env file
Sanitizes secret values (replaces with placeholders)
Generates .env.example with safe defaults

Example:

bash

undefined

为你的环境变量创建文档：

bash

python3 scripts/validate_env.py .env --generate-example .env.example

功能说明：

读取你的.env文件
清理密钥值（替换为占位符）
生成包含安全默认值的.env.example

示例：

bash

undefined

Input: .env

输入：.env

DATABASE_URL=postgresql://user:pass@localhost/db # pragma: allowlist secret STRIPE_SECRET_KEY=sk_live_abc123xyz NEXT_PUBLIC_API_URL=https://api.example.com

Output: .env.example

输出：.env.example

DATABASE_URL=postgresql://user:password@localhost/dbname # pragma: allowlist secret STRIPE_SECRET_KEY=your_stripe_secret_key_here NEXT_PUBLIC_API_URL=https://api.example.com


**Security note:** env-manager detects common secret patterns and replaces them with safe placeholders.

DATABASE_URL=postgresql://user:password@localhost/dbname # pragma: allowlist secret STRIPE_SECRET_KEY=your_stripe_secret_key_here NEXT_PUBLIC_API_URL=https://api.example.com


**安全提示：** env-manager可检测常见密钥模式，并将其替换为安全占位符。

CI/CD Integration

CI/CD集成

Get machine-readable JSON output for automated workflows:

bash

python3 scripts/validate_env.py .env.example --strict --json

JSON output format:

json

{
  "valid": true,
  "errors": [],
  "warnings": [],
  "stats": {
    "total_vars": 15,
    "errors": 0,
    "warnings": 0
  }
}

Exit codes:

```
0
```
: Validation passed
```
1
```
: Validation errors found
```
2
```
: Missing required file
```
3
```
: Warnings found (only in --strict mode)

GitHub Actions example:

yaml

name: Validate Environment Variables

on: [push, pull_request]

jobs:
  validate-env:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Validate .env.example
        run: |
          python3 scripts/validate_env.py .env.example --strict --json
        working-directory: ./path/to/skill

      - name: Check for framework-specific issues
        run: |
          python3 scripts/validate_env.py .env.example --framework nextjs --json
        working-directory: ./path/to/skill

获取机器可读的JSON输出以用于自动化工作流：

bash

python3 scripts/validate_env.py .env.example --strict --json

JSON输出格式：

json

{
  "valid": true,
  "errors": [],
  "warnings": [],
  "stats": {
    "total_vars": 15,
    "errors": 0,
    "warnings": 0
  }
}

退出码：

```
0
```
：验证通过
```
1
```
：检测到验证错误
```
2
```
：缺失必要文件
```
3
```
：检测到警告（仅在--strict模式下）

GitHub Actions示例：

yaml

name: Validate Environment Variables

on: [push, pull_request]

jobs:
  validate-env:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - name: Validate .env.example
        run: |
          python3 scripts/validate_env.py .env.example --strict --json
        working-directory: ./path/to/skill

      - name: Check for framework-specific issues
        run: |
          python3 scripts/validate_env.py .env.example --framework nextjs --json
        working-directory: ./path/to/skill

Strict Mode

严格模式

Treat warnings as errors (useful for CI/CD):

bash

python3 scripts/validate_env.py .env --strict

When to use:

Pre-deployment validation
CI/CD pipelines
Release gates
Team standard enforcement

将警告视为错误（适用于CI/CD场景）：

bash

python3 scripts/validate_env.py .env --strict

适用场景：

部署前验证
CI/CD流水线
发布准入检查
团队规范强制执行

Quiet Mode

静默模式

Show only errors, suppress warnings:

bash

python3 scripts/validate_env.py .env --quiet

When to use:

You've already reviewed warnings
Automated scripts that only care about errors
Noisy environments where warnings are distracting

仅显示错误，隐藏警告：

bash

python3 scripts/validate_env.py .env --quiet

适用场景：

已完成警告审查
仅关注错误的自动化脚本
警告信息过多的嘈杂环境

Supported Frameworks

支持的框架

Framework	Prefix	Client-Exposed	Notes
Next.js	`NEXT_PUBLIC_*`	Yes	Auto-exposed in browser
Vite	`VITE_*`	Yes	Bundled into client code
React (CRA)	`REACT_APP_*`	Yes	Embedded in production build
Node.js	N/A	No	Server-side only
Flask	N/A	No	Server-side only

Security warning: Never put secrets in client-exposed variables (NEXT_PUBLIC_, VITE_, REACT_APP_). env-manager will warn you if it detects common secret patterns.

框架	前缀	客户端可访问	说明
Next.js	`NEXT_PUBLIC_*`	是	自动暴露至浏览器
Vite	`VITE_*`	是	打包到客户端代码中
React (CRA)	`REACT_APP_*`	是	嵌入到生产构建包中
Node.js	N/A	否	仅服务端可见
Flask	N/A	否	仅服务端可见

安全警告： 绝不要将密钥放入客户端可访问的变量（NEXT_PUBLIC_、VITE_、REACT_APP_）中。若检测到常见密钥模式，env-manager会发出警告。

CLI Reference

CLI参考

Command Structure

命令结构

bash

python3 scripts/validate_env.py <file> [options]

bash

python3 scripts/validate_env.py <file> [options]

Options

选项

Option	Description	Example
`--compare-with FILE`	Compare with .env.example	`--compare-with .env.example`
`--framework {nextjs\|vite\|react\|nodejs\|flask\|generic}`	Framework-specific validation	`--framework nextjs`
`--strict`	Treat warnings as errors	`--strict`
`--json`	JSON output for automation	`--json`
`--quiet`	Only show errors	`--quiet`
`--generate-example OUTPUT`	Generate .env.example	`--generate-example .env.example`

选项	描述	示例
`--compare-with FILE`	与.env.example对比	`--compare-with .env.example`
`--framework {nextjs\|vite\|react\|nodejs\|flask\|generic}`	框架特定验证	`--framework nextjs`
`--strict`	将警告视为错误	`--strict`
`--json`	输出JSON格式以用于自动化	`--json`
`--quiet`	仅显示错误	`--quiet`
`--generate-example OUTPUT`	生成.env.example文件	`--generate-example .env.example`

Exit Codes

退出码

Code	Meaning	When
`0`	Success	No errors (warnings OK unless --strict)
`1`	Validation errors	Structural issues, duplicates, etc.
`2`	File not found	Specified .env file doesn't exist
`3`	Warnings in strict mode	Warnings exist and --strict enabled

代码	含义	触发场景
`0`	成功	无错误（除非启用--strict，否则警告不影响结果）
`1`	验证错误	存在结构问题、重复键等
`2`	文件未找到	指定的.env文件不存在
`3`	严格模式下检测到警告	存在警告且已启用--strict模式

Common Use Cases

常见使用场景

Scenario 1: New Developer Onboarding

场景1：新开发者入职配置

bash

undefined

bash

undefined

New developer clones repo

新开发者克隆仓库

git clone <repo> cd <project>

Copy example and fill in values

复制示例文件并填写值

cp .env.example .env

Edit .env with actual values...

编辑.env文件填入实际值...

Validate setup

验证配置

python3 scripts/validate_env.py .env --compare-with .env.example

If missing variables, fix them

若存在缺失变量则修复

Validation passes ✅

验证通过 ✅

undefined

undefined

Scenario 2: Pre-Deployment Check

场景2：部署前检查

bash

undefined

bash

undefined

Before deploying to Vercel/Railway/Heroku

部署到Vercel/Railway/Heroku之前

python3 scripts/validate_env.py .env.production --framework nextjs --strict

Fix any errors

修复所有错误

Deploy with confidence ✅

放心部署 ✅

undefined

undefined

Scenario 3: Security Audit

场景3：安全审计

bash

undefined

bash

undefined

Check for accidentally exposed secrets

检查是否存在意外暴露的密钥

python3 scripts/validate_env.py .env.local --framework nextjs

Look for warnings like:

留意如下警告：

⚠️ NEXT_PUBLIC_STRIPE_SECRET: Contains potential secret in client-exposed variable

⚠️ NEXT_PUBLIC_STRIPE_SECRET: 客户端可访问变量中包含潜在密钥

undefined

undefined

Scenario 4: Team Documentation

场景4：团队文档维护

bash

undefined

bash

undefined

After adding new environment variable

添加新环境变量后

echo "NEW_API_KEY=abc123" >> .env

Regenerate .env.example

重新生成.env.example

python3 scripts/validate_env.py .env --generate-example .env.example

Commit updated .env.example

提交更新后的.env.example

git add .env.example git commit -m "docs: add NEW_API_KEY to environment variables"

undefined

git add .env.example git commit -m "docs: 新增NEW_API_KEY环境变量"

undefined

Scenario 5: CI/CD Quality Gate

场景5：CI/CD质量门禁

yaml

undefined

yaml

undefined

In your CI pipeline

在CI流水线中

name: Validate environment configuration run: | python3 scripts/validate_env.py .env.example --strict --json > validation.json

Fail pipeline if validation fails

if [ $? -ne 0 ]; then cat validation.json exit 1 fi

undefined

name: 验证环境配置 run: | python3 scripts/validate_env.py .env.example --strict --json > validation.json

若验证失败则终止流水线

if [ $? -ne 0 ]; then cat validation.json exit 1 fi

undefined

Performance

性能

env-manager is designed for speed:

Benchmarks:

Validates 1000 variables in 0.025s
80x faster than 2s target
Zero external dependencies
Minimal memory footprint

Why it matters:

Fast feedback during development
No CI/CD slowdown
Works in resource-constrained environments

env-manager专为速度设计：

基准测试：

验证1000个变量仅需0.025秒
比目标速度快80倍
无外部依赖
内存占用极低

性能优势：

开发过程中快速反馈
不会拖慢CI/CD速度
可在资源受限环境中运行

Security Notes

安全说明

Critical security features:

Never Logs Secrets: env-manager NEVER displays actual secret values in output
Client-Exposure Detection: Warns when secrets are in NEXT_PUBLIC_, VITE_, REACT_APP_ variables
Secret Sanitization: When generating .env.example, replaces secrets with safe placeholders
No Network Calls: All validation is local, no data leaves your machine

Security-audited: This skill has undergone security review. See references/security.md for details.

Best practices:

Never commit .env files with secrets
Always use .env.example for documentation
Use platform secret managers (Vercel, Railway, etc.) for production
Validate before every deployment
Run security scan regularly

核心安全特性：

绝不记录密钥：env-manager绝不会在输出中显示实际密钥值
客户端暴露检测：当密钥出现在NEXT_PUBLIC_、VITE_、REACT_APP_变量中时发出警告
密钥清理：生成.env.example时，会将密钥替换为安全占位符
无网络请求：所有验证均在本地完成，数据不会离开你的机器

安全审计： 本工具已通过安全审查。详情请见references/security.md。

最佳实践：

绝不要提交包含密钥的.env文件
始终使用.env.example作为文档
生产环境使用平台密钥管理器（Vercel、Railway等）
每次部署前都要验证
定期运行安全扫描

Common Issues

常见问题

"Missing equals sign" error

"Missing equals sign"错误

Cause: Line in .env doesn't have = separator

Fix:

bash

undefined

原因： .env文件中某一行没有使用=分隔符

修复：

bash

undefined

❌ Bad

❌ 错误写法

API_KEY

✅ Good

✅ 正确写法

API_KEY=your_key_here

undefined

API_KEY=your_key_here

undefined

"Duplicate key" error

"Duplicate key"错误

Cause: Same variable defined multiple times

Fix:

bash

undefined

原因： 同一个变量被多次定义

修复：

bash

undefined

❌ Bad

❌ 错误写法

API_KEY=value1 API_KEY=value2

✅ Good

✅ 正确写法

API_KEY=value2

undefined

API_KEY=value2

undefined

"Invalid variable name" warning

"Invalid variable name"警告

Cause: Variable name doesn't follow UPPERCASE_WITH_UNDERSCORES convention

Fix:

bash

undefined

原因： 变量名不符合大写字母加下划线的命名规范

修复：

bash

undefined

❌ Bad

❌ 错误写法

apiKey=value api-key=value

✅ Good

✅ 正确写法

API_KEY=value

undefined

API_KEY=value

undefined

"Potential secret in client-exposed variable" warning

"Potential secret in client-exposed variable"警告

Cause: NEXT_PUBLIC_, VITE_, or REACT_APP_ variable contains secret-like value

Fix:

bash

undefined

原因： NEXT_PUBLIC_、VITE_或REACT_APP_前缀变量中包含类密钥值

修复：

bash

undefined

❌ Bad (secret exposed to client!)

❌ 错误写法（密钥暴露给客户端！）

NEXT_PUBLIC_STRIPE_SECRET=sk_live_abc123

✅ Good (server-side only)

✅ 正确写法（仅服务端可见）

STRIPE_SECRET_KEY=sk_live_abc123 NEXT_PUBLIC_STRIPE_PUBLISHABLE=pk_live_xyz789

undefined

STRIPE_SECRET_KEY=sk_live_abc123 NEXT_PUBLIC_STRIPE_PUBLISHABLE=pk_live_xyz789

undefined

"Empty value" warning

"Empty value"警告

Cause: Variable has no value

Fix:

bash

undefined

原因： 变量无值

修复：

bash

undefined

❌ Bad

❌ 错误写法

DATABASE_URL=

✅ Good (if optional, document it)

✅ 正确写法（若为可选变量请注明）

DATABASE_URL= # Optional, uses SQLite if not set

DATABASE_URL= # 可选，未设置时使用SQLite

✅ Better

✅ 更优写法

DATABASE_URL=postgresql://localhost/mydb

undefined

DATABASE_URL=postgresql://localhost/mydb

undefined

File not found error

文件未找到错误

Cause: Specified .env file doesn't exist

Fix:

bash

undefined

原因： 指定的.env文件不存在

修复：

bash

undefined

Check file exists

检查文件是否存在

ls -la .env

Or create it

或创建文件

touch .env

undefined

touch .env

undefined

Troubleshooting

故障排除

Validation passes locally but fails in CI

本地验证通过但CI中失败

Check:

Line endings (CRLF vs LF)
File encoding (UTF-8 expected)
File permissions
Python version (3.7+ required)

检查项：

行尾格式（CRLF vs LF）
文件编码（需为UTF-8）
文件权限
Python版本（要求3.7+）

Warnings about client-exposed variables

关于客户端可访问变量的警告

This is intentional! env-manager is warning you that variables like NEXT_PUBLIC_API_KEY will be visible in the browser.

Options:

Move secret to server-side variable (remove NEXT_PUBLIC_ prefix)
Use public/publishable keys only in client-exposed variables
If truly not a secret, ignore the warning

这是有意设计的！ env-manager会警告你类似NEXT_PUBLIC_API_KEY的变量会在浏览器中可见。

解决方案：

将密钥移至服务端变量（移除NEXT_PUBLIC_前缀）
仅在客户端可访问变量中使用公钥/可发布密钥
若确实不是密钥，可忽略警告

.env.example generation replaces too much

.env.example生成时过度清理

env-manager is conservative about secrets. If it over-sanitizes:

Manually edit .env.example after generation
Use specific placeholder values in .env that won't trigger sanitization

env-manager对密钥的检测较为保守。若出现过度清理：

生成后手动编辑.env.example
在.env中使用不会触发清理的特定占位符值

Advanced Usage

高级用法

Custom Validation Patterns

自定义验证规则

See references/validation.md for advanced validation patterns.

高级验证规则请见references/validation.md。

Platform-Specific Deployment

平台特定部署

See references/synchronization.md for Vercel, Railway, Heroku integration patterns.

Vercel、Railway、Heroku集成模式请见references/synchronization.md。

Framework-Specific Guides

框架特定指南

See references/frameworks.md for comprehensive framework guides.

全面的框架指南请见references/frameworks.md。

Integration with Claude MPM

与Claude MPM集成

env-manager is a bundled skill in Claude MPM. Agents can use it for:

Pre-deployment validation
Security scanning
Environment setup verification
Documentation generation

See INTEGRATION.md for agent integration patterns.

env-manager是Claude MPM的内置工具。Agent可将其用于：

部署前验证
安全扫描
环境配置验证
文档生成

Agent集成模式请见INTEGRATION.md。

Contributing

贡献指南

env-manager follows Claude MPM contribution guidelines:

Run
```
make lint-fix
```
during development
Run
```
make quality
```
before commits
Add tests for new features (85%+ coverage required)
Update documentation

See CONTRIBUTING.md for details.

env-manager遵循Claude MPM贡献规范：

开发过程中运行
```
make lint-fix
```
提交前运行
```
make quality
```
为新功能添加测试（要求覆盖率85%+）
更新文档

详情请见CONTRIBUTING.md。

License

许可证

MIT License - Part of Claude MPM project

MIT许可证 - Claude MPM项目的一部分

Support

支持

Issues: Report bugs via GitHub Issues
Documentation: See references/ directory
Examples: See examples/ directory
Integration: See INTEGRATION.md

Version: 1.0.0 Status: Stable, Security-Audited Test Coverage: 85%+ Performance: 80x faster than target

问题反馈：通过GitHub Issues提交bug
文档：请查看references/目录
示例：请查看examples/目录
集成：请查看INTEGRATION.md

版本：1.0.0 状态：稳定，已通过安全审计 测试覆盖率：85%+ 性能：比目标速度快80倍