path-source 0.1.1
Read files in Node, or fetch URLs in browser, as standard WhatWG streams.
path-source@0.1.1 was published on 2016-09-07. Its manifest declares 2 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All path-source versions · Permanent reference to 0.1.1 · Latest release
Package specifications
| Version | 0.1.1 |
|---|---|
| License declaration | BSD-3-Clause |
| Published | 2016-09-07T22:07:23.220Z |
| Node.js requirement | Not declared |
| 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 | index.js |
| Default entry | index.node.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | 5 |
| Repository forks | 0 |
Install path-source 0.1.1
npm install path-source@0.1.1 pnpm add path-source@0.1.1 yarn add path-source@0.1.1
Runtime dependencies
- array-source 0.0
- file-source 0.6
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-source@0.0.4 — direct
- file-source@0.6.1 — direct
- stream-source@0.3.5 — 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/17 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| SAST | 0/10 — no SAST tool detected |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/path-source/0.1.1 — retrieved 2026-10-29T16:19:50.260Z
- https://api.deps.dev/v3/systems/npm/packages/path-source/versions/0.1.1 — retrieved 2026-10-29T16:19:50.863Z
- https://api.deps.dev/v3/projects/github.com%2Fmbostock%2Fpath-source — retrieved 2026-10-29T13:01:45.291Z
- https://api.deps.dev/v3/systems/npm/packages/path-source/versions/0.1.1:dependencies — retrieved 2026-10-29T16:19:50.901Z