env-cmd

Executes a command using the environment variables in an env file

env-cmd@11.0.0 was published on 2025-08-23. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.10.0.

All env-cmd versions · Permanent reference to 11.0.0

Package specifications

Version11.0.0
License declarationMIT
Published2025-08-23T03:31:34.652Z
Node.js requirement>=20.10.0
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size53.91 KiB
Published file count33
Package typemodule
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies8
Repository stars1816
Repository forks69

Install env-cmd 11.0.0

npm install env-cmd@11.0.0
pnpm add env-cmd@11.0.0
yarn add env-cmd@11.0.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Code-Review8/10 — Found 7/8 approved changesets -- score normalized to 8
Binary-Artifacts10/10 — no binaries found in the repo
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
Security-Policy0/10 — security policy file not detected
License10/10 — license file detected
Branch-Protection6/10 — branch protection is not maximal on development and all release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness