path-segments
Get n specific segments of a file path, e.g. first 2, last 3, etc.
path-segments@0.1.1 was published on 2014-06-26. Its manifest declares 2 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 path-segments versions · Permanent reference to 0.1.1
Package specifications
| Version | 0.1.1 |
|---|---|
| License declaration | Not declared |
| Published | 2014-06-26T04:03:05.582Z |
| Node.js requirement | >=0.10.0 |
| 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 | 5 |
| Repository forks | 0 |
Install path-segments 0.1.1
npm install path-segments@0.1.1 pnpm add path-segments@0.1.1 yarn add path-segments@0.1.1
Runtime dependencies
- lodash ^2.4.1
- parse-filepath ^0.3.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.
- ends-with@0.2.0 — indirect
- lodash@2.4.2 — direct
- normalize-path@2.1.1 — indirect
- parse-filepath@0.3.1 — direct
- path-ends-with@0.2.3 — indirect
- remove-trailing-separator@1.1.0 — 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/2 approved changesets -- score normalized to 0 |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| 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/path-segments/0.1.1 — retrieved 2026-10-29T19:47:04.749Z
- https://api.deps.dev/v3/systems/npm/packages/path-segments/versions/0.1.1 — retrieved 2026-10-29T19:47:05.458Z
- https://api.deps.dev/v3/systems/npm/packages/path-segments/versions/0.1.1:dependencies — retrieved 2026-10-29T19:47:05.652Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fpath-segments — retrieved 2026-10-29T19:47:05.667Z