yeoman-doctor 1.3.1

Detect potential issues with users system that could prevent Yeoman from working correctly

yeoman-doctor@1.3.1 was published on 2015-01-25. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.

All yeoman-doctor versions · Permanent reference to 1.3.1 · Latest release

Package specifications

Version1.3.1
License declarationBSD
Published2015-01-25T22:41:36.061Z
Node.js requirement>=0.10.0
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entrylib/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies25
Repository stars64
Repository forks18

Install yeoman-doctor 1.3.1

npm install yeoman-doctor@1.3.1
pnpm add yeoman-doctor@1.3.1
yarn add yeoman-doctor@1.3.1

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.

Code-Review4/10 — Found 13/30 approved changesets -- score normalized to 4
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Pinned-Dependencies5/10 — dependency not pinned by hash detected -- score normalized to 5
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
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
SAST7/10 — SAST tool detected but not run on all commits

Evidence and freshness