envify 3.4.0
Selectively replace Node-style environment variables with plain strings.
envify@3.4.0 was published on 2015-03-16. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All envify versions · Permanent reference to 3.4.0 · Latest release
Package specifications
| Version | 3.4.0 |
|---|---|
| License declaration | MIT |
| Published | 2015-03-16T19:49:09.622Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 897 |
| Repository forks | 57 |
Install envify 3.4.0
npm install envify@3.4.0 pnpm add envify@3.4.0 yarn add envify@3.4.0
Runtime dependencies
- through ~2.3.4
- jstransform ^10.0.1
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.
- amdefine@1.0.1 — indirect
- base62@0.1.1 — indirect
- esprima-fb@13001.1001.0-dev-harmony-fb — indirect
- jstransform@10.1.0 — direct
- source-map@0.1.31 — indirect
- through@2.3.8 — direct
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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 2/10 — Found 8/27 approved changesets -- score normalized to 2 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 0/10 — license file not detected |
| Security-Policy | 0/10 — security policy file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/envify/3.4.0 — retrieved 2026-10-29T15:15:42.893Z
- https://api.deps.dev/v3/projects/github.com%2Fhughsk%2Fenvify — retrieved 2026-10-29T15:14:37.265Z
- https://api.deps.dev/v3/systems/npm/packages/envify/versions/3.4.0 — retrieved 2026-10-29T15:15:43.439Z
- https://api.deps.dev/v3/systems/npm/packages/envify/versions/3.4.0:dependencies — retrieved 2026-10-29T15:15:43.431Z