yeoman-environment 4.4.2

Handles the lifecyle and bootstrapping of generators in a specific environment

yeoman-environment@4.4.2 was published on 2024-10-11. Its manifest declares 21 runtime dependencies and 2 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^18.17.0 || >=20.5.0.

All yeoman-environment versions · Permanent reference to 4.4.2 · View npm registry JSON · Latest release

Package specifications

Version4.4.2
License declarationBSD-2-Clause
Published2024-10-11T19:14:25.316Z
Node.js requirement^18.17.0 || >=20.5.0
Type declarationsBundled declarations
Runtime dependency count21
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size118.10 KiB
Published file count38
Package typemodule
ES module entryNot declared
Default entry./dist/index.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies358
Repository stars132
Repository forks72

Install yeoman-environment 4.4.2

npm install yeoman-environment@4.4.2
pnpm add yeoman-environment@4.4.2
yarn add yeoman-environment@4.4.2

Runtime dependencies

Peer requirements

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.

Known direct advisories

OpenSSF repository checks

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

Code-Review0/10 — Found 0/11 approved changesets -- score normalized to 0
Maintained10/10 — 17 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies3/10 — dependency not pinned by hash detected -- score normalized to 3
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Security-Policy10/10 — security policy file detected
Packaging10/10 — packaging workflow detected
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness