cwd 0.5.1
Node.js util for easily getting the current working directory of a project based on package.json or the given path.
cwd@0.5.1 was published on 2015-03-05. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.8.
All cwd versions · Permanent reference to 0.5.1 · Latest release
Package specifications
| Version | 0.5.1 |
|---|---|
| License declaration | MIT |
| Published | 2015-03-05T18:48:44.272Z |
| Node.js requirement | >=0.8 |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| 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 | 9 |
| Repository stars | 13 |
| Repository forks | 2 |
Install cwd 0.5.1
npm install cwd@0.5.1 pnpm add cwd@0.5.1 yarn add cwd@0.5.1
Runtime dependencies
- look-up ^0.2.0
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.
- array-differ@1.0.0 — indirect
- array-union@1.0.2 — indirect
- array-uniq@1.0.3 — indirect
- look-up@0.2.3 — direct
- lru-cache@2.7.3 — indirect
- minimatch@1.0.0 — indirect
- multimatch@1.0.1 — indirect
- normalize-path@0.3.0 — indirect
- sigmund@1.0.1 — indirect
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-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/cwd/0.5.1 — retrieved 2026-10-29T23:25:15.408Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fcwd — retrieved 2026-10-29T21:24:11.356Z
- https://api.deps.dev/v3/systems/npm/packages/cwd/versions/0.5.1:dependencies — retrieved 2026-10-29T23:25:15.961Z
- https://api.deps.dev/v3/systems/npm/packages/cwd/versions/0.5.1 — retrieved 2026-10-29T23:25:15.980Z