std-env provides runtime-agnostic JavaScript utilities for detecting the current JavaScript runtime, CI/CD provider, and whether the code is running inside an AI coding agent. It also includes environment and platform flags (such as TTY availability, CI, development/production mode, and OS) that can be used by CLI or app code to adapt behavior.
Project status
- Actively maintained: Yes. There was an upstream push on 2026-07-08, and a recent tagged update v4.2.0 on 2026-07-07, indicating ongoing development rather than a dormant period.
- Update cadence: Recent cadence is fairly tight, with v4.2.0 (2026-07-07) following v4.1.0 (2026-04-15) (about 3 months), and earlier updates roughly every few months (2026-03-10, 2026-02-17).
AI summary generated
Recent updates
v4.2.0
v4.2.0 adds support for the Junie coding agent and adjusts agent detection logic for Kiro. Specifically, Kiro detection is now gated to avoid misidentifying the Kiro IDE integrated terminal as an agent.
Featuresv4.1.0
std-env v4.1.0 adds support for detecting the EdgeOne Pages CI environment. The change extends the internal provider mapping and the exported ProviderName union to include the new provider. No other code behavior changes are visible in the provided diff.
Featuresv4.0.0
Release v4.0.0 finalizes the previously published v4.0.0-rc.1 version and updates the package metadata. The code diff provided shows mostly documentation-level changes (types/comments, README/CHANGELOG wording) plus an apparent addition of a runtime-agnostic `process` shim export in `src/env.ts`.
Featuresv4.0.0-rc.1
This release introduces AI coding agent detection and adds support for `MODE` when determining `isDevelopment` and `isProduction`. It also performs a major modernization refactor that removes the previous env/process shim implementation and switches the build output to ESM-only.
BreakingFeaturesv3.10.0
v3.10.0 adds runtime and provider detection improvements, specifically for DENO_DEPLOY (Deno Deploy EA) and Google Cloud Run/Jobs. The release notes also mention stricter type checks and switching the package to ESM via package.json "type": "module". The code diff shows additional build and TypeScript/module-resolution related changes that are not fully captured in the release notes.
BreakingFeaturesv3.9.0
Release v3.9.0 adds Cloudflare Workers CI detection by extending the set of known CI providers. In addition to that small runtime-facing change, the release updates multiple development toolchain dependencies and the pnpm package manager version.
BreakingFeaturesv3.8.1
Release v3.8.1 primarily updates std-env's provider detection to recognize the CODESANDBOX_HOST environment variable. The code diff also includes CI/development workflow adjustments and a set of devDependency and tooling version bumps (including pnpm), which are not fully captured in the provided release notes.
v3.8.0
v3.8.0 adds runtime provider detection for Deno Deploy and Firebase App Hosting. It also removes support for the Lagon runtime. Several build and tooling/development dependencies were updated as part of the release.
BreakingFeaturesv3.7.0
v3.7.0 adds detection for the Railway deployment provider and improves runtime detection so Bun is prioritized over Node. It also clarifies the semantics of the `isNode` flag, especially when Bun or Deno run with Node.js compatibility mode.
Featuresv3.6.0
v3.6.0 adds support for two new hosted execution providers, zeabur and codesphere, and includes a small type improvement for the exported runtime value. It also changes the environment-based logic used to decide whether ANSI color output should be enabled.
Featuresv3.5.0
This release primarily documents adding a new runtime CI provider for AWS Amplify. The code diff confirms the new provider and associated environment variable mapping, but it also includes additional changes (type surface area, CI workflow action upgrades, and significant devDependency updates) that are not mentioned in the release notes.
BreakingFeatures