env-ci

Get environment variables exposed by CI services

env-ci@11.2.0 was published on 2025-09-01. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is ^18.17 || >=20.6.1.

All env-ci versions · Permanent reference to 11.2.0

Package specifications

Version11.2.0
License declarationMIT
Published2025-09-01T15:33:26.382Z
Node.js requirement^18.17 || >=20.6.1
Type declarationsNot declared
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size52.26 KiB
Published file count38
Package typemodule
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies18
Repository stars242
Repository forks47

Install env-ci 11.2.0

npm install env-ci@11.2.0
pnpm add env-ci@11.2.0
yarn add env-ci@11.2.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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies10/10 — all dependencies are pinned
Maintained10/10 — 25 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness