get-installed-path 4.0.7
Get installation path where the given package is installed. Works for globally and locally installed packages
get-installed-path@4.0.7 was published on 2017-10-10. 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 >=6.
All get-installed-path versions · Permanent reference to 4.0.7 · Latest release
Package specifications
| Version | 4.0.7 |
|---|---|
| License declaration | MIT |
| Published | 2017-10-10T21:47:13.375Z |
| Node.js requirement | >=6 |
| 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 | ./dist/index.es.js |
| Default entry | ./dist/index.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 10 |
| Repository stars | 42 |
| Repository forks | 7 |
Install get-installed-path 4.0.7
npm install get-installed-path@4.0.7 pnpm add get-installed-path@4.0.7 yarn add get-installed-path@4.0.7
Runtime dependencies
- global-modules 1.0.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.
- expand-tilde@2.0.2 — indirect
- global-modules@1.0.0 — direct
- global-prefix@1.0.2 — indirect
- homedir-polyfill@1.0.3 — indirect
- ini@1.3.8 — indirect
- is-windows@1.0.2 — indirect
- isexe@2.0.0 — indirect
- parse-passwd@1.0.0 — indirect
- resolve-dir@1.0.1 — indirect
- which@1.3.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.
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
|---|---|
| Code-Review | 0/10 — Found 0/30 approved changesets -- score normalized to 0 |
| 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 | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/get-installed-path/4.0.7 — retrieved 2026-10-29T22:53:09.305Z
- https://api.deps.dev/v3/projects/github.com%2FtunnckoCore%2Fget-installed-path — retrieved 2026-10-29T18:54:29.154Z
- https://api.deps.dev/v3/systems/npm/packages/get-installed-path/versions/4.0.7 — retrieved 2026-10-29T22:53:09.828Z
- https://api.deps.dev/v3/systems/npm/packages/get-installed-path/versions/4.0.7:dependencies — retrieved 2026-10-29T22:53:09.848Z