Spekra Reliability Vector #9 • Zero-Exposure Static Drift Engine

Stop 2 AM Deployment Outages.
Statically Verify Environment Contracts.

Over 25% of cloud deploy failures are triggered by undeclared environment variables, syntax mismatches, or accidental client browser credential exposures. EnvProof reconciles code against manifests in <500ms without ever reading raw secrets.

< 500ms
Zero-Dependency AST Scan Speed
0 Secrets Read
Strict Zero-Exposure Invariant
100% Offline
Cryptographic HMAC License Validation
Auto Leak-Guard
Blocks NEXT_PUBLIC_ Private Keys

Interactive Environment Drift Simulator

Select an architectural stack scenario below, inspect the code and manifest discrepancies, and run a live simulated scan to witness real-time drift resolution.

src/components/CheckoutWidget.tsx Application Code AST
.env.example Public Configuration Template
Environment Health Index
92 / 100
A (SOUND)
LOW RISK
Missing in Template 1
Secret Leaks 0
Diagnostic Findings 1 detected
Deterministic SHA-256 Seal VERIFIED
8f94bc32e87903c7d6a5e1104e67f091bc829471ab634281

Zero-Config Quickstart

Run directly with npx or install into your GitHub Actions workflow in under 30 seconds.

Run an instant zero-exposure scan on your repository without installing anything:

# 60-second diagnostic scan on local repository
npx envproof scan

# Verbose mode with line-by-line file references
npx envproof scan --verbose

# Export interactive HTML audit report
npx envproof scan --html --out env-audit.html

Live Trust Badge Studio

Embed dynamic high-DPI verification badges into your repository READMEs, status dashboards, and internal developer portals.

Live High-DPI Badge Preview
[![EnvProof Config Drift](https://envproof.spekra.in/v1/badge/default)](https://envproof.spekra.in)

SOC 2 CC6.8 & ISO 27001 Auditor Pack

Satisfy strict enterprise change management audits with tamper-proof cryptographic attestation bundles.

SOC 2 Type II CC6.8

Configuration baseline integrity & logical access: Statically verifies that application environments contain only authorized, versioned schema definitions with zero undeclared secrets.

ISO/IEC 27001 A.12.1.2

Change documentation and management: Verifies complete reconciliation across code, templates, Docker compose manifests, and CI/CD workflows before deployments proceed.

Cryptographic SHA-256 Seal

Every audit bundle produces a deterministic SHA-256 seal computed over canonicalized schema JSON, guaranteeing non-repudiation for security and compliance reviewers.

Commercial Licensing & Pricing

Zero-dependency, local-first engine with offline HMAC signed license tokens. No phone-home servers required.

Community
$0 / forever

1 Developer / Local Machine

  • ✓npx envproof scan
  • ✓Terminal 0-100 Score
  • ✓.env.example Auto-Sync
  • ✕CI/CD PR Gate
  • ✕SOC 2 Auditor Pack
Starter
$99 / year

1 Repository / 5 Team Seats

  • ✓Everything in Community
  • ✓GitHub Action PR Gate
  • ✓Signed JSON Contract
  • ✓Dynamic Trust Badges
  • ✕SOC 2 Auditor Pack
Most Popular
Pro
$299 / year

Unlimited Repos / 20 Seats

  • ✓Everything in Starter
  • ✓Standalone HTML Reports
  • ✓Multi-Framework AST
  • ✓SOC 2 CC6.8 Auditor Pack
  • ✓4-Hour Support SLA
Enterprise
$699 / year

Unlimited Repos & Seats

  • ✓Everything in Pro
  • ✓ISO 27001 A.12.1.2 Pack
  • ✓Custom Variable Rules
  • ✓Webhook Alert Dispatch
  • ✓1-Hour Critical SLA

Frequently Asked Questions

How does EnvProof verify environment variables without reading actual secrets?

EnvProof strictly operates on code Abstract Syntax Trees (AST) and static manifest files. It extracts variable identifier names (e.g. process.env.DATABASE_URL) and checks for their existence in .env.example, Dockerfiles, and CI definitions. It never opens production .env files or queries secret managers.

How does offline HMAC signed licensing work?

EnvProof licenses (ep_lic_...) are self-contained, base64url-encoded JSON payloads cryptographically signed with SHA-256 HMAC tokens. The CLI validates the digital signature and expiration date locally without ever phoning home or requiring internet access during CI/CD execution.

What frontend bundler prefixes are checked for leaks?

EnvProof inspects Next.js (NEXT_PUBLIC_), Vite (VITE_), Create React App (REACT_APP_), Nuxt (NUXT_PUBLIC_), Gatsby (GATSBY_), and Expo (EXPO_PUBLIC_). Any variable with these prefixes containing sensitive keywords like SECRET, PASSWORD, PRIVATE_KEY, or MASTER_KEY is flagged as a CRITICAL leak hazard.

Can I auto-fix configuration drift automatically?

Yes. Running npx envproof sync --out .env.example parses your application code and automatically generates or updates your .env.example template with inferred types, default values, and source comments.