getit 0.4.2
Retrieve local and remote files through a simple interface
getit@0.4.2 was published on 2014-05-13. Its manifest declares 4 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 getit versions · Permanent reference to 0.4.2 · Latest release
Package specifications
| Version | 0.4.2 |
|---|---|
| License declaration | MIT |
| Published | 2014-05-13T06:26:57.878Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 4 |
| 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 | 8 |
| Repository stars | 6 |
| Repository forks | 0 |
Install getit 0.4.2
npm install getit@0.4.2 pnpm add getit@0.4.2 yarn add getit@0.4.2
Runtime dependencies
- debug *
- mkdirp ~0.5
- hyperquest ~0.3
- urlish ~0.1
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.
- debug@4.4.3 — direct
- duplexer@0.1.2 — indirect
- hyperquest@0.3.0 — direct
- minimist@1.2.8 — indirect
- mkdirp@0.5.6 — direct
- ms@2.1.3 — indirect
- through@2.2.7 — indirect
- urlish@0.1.0 — direct
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/28 approved changesets -- score normalized to 0 |
|---|---|
| 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 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Security-Policy | 0/10 — security policy file not 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 |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/getit/0.4.2 — retrieved 2026-10-30T14:17:34.221Z
- https://api.deps.dev/v3/systems/npm/packages/getit/versions/0.4.2 — retrieved 2026-10-30T14:17:34.762Z
- https://api.deps.dev/v3/systems/npm/packages/getit/versions/0.4.2:dependencies — retrieved 2026-10-30T14:17:34.793Z
- https://api.deps.dev/v3/projects/github.com%2FDamonOehlman%2Fgetit — retrieved 2026-10-30T14:17:35.326Z