git-fetch-pack 0.0.2
git's smart fetch-pack protocol
git-fetch-pack@0.0.2 was published on 2013-05-04. 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 git-fetch-pack versions · Permanent reference to 0.0.2 · Latest release
Package specifications
| Version | 0.0.2 |
|---|---|
| License declaration | MIT |
| Published | 2013-05-04T23:46:05.324Z |
| 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 | 7 |
| Repository stars | 7 |
| Repository forks | 0 |
Install git-fetch-pack 0.0.2
npm install git-fetch-pack@0.0.2 pnpm add git-fetch-pack@0.0.2 yarn add git-fetch-pack@0.0.2
Runtime dependencies
- emit-function 0.0.2
- through ~2.2.7
- git-packed-ref-parse 0.0.0
- bops 0.0.2
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.
- base64-js@0.0.2 — indirect
- bops@0.0.2 — direct
- emit-function@0.0.2 — direct
- git-packed-ref-parse@0.0.0 — direct
- line-stream@0.0.0 — indirect
- through@2.2.7 — direct
- to-utf8@0.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.
| 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 |
| Code-Review | 0/10 — Found 0/17 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 |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 0/10 — license file not detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/git-fetch-pack/0.0.2 — retrieved 2026-10-29T21:28:16.730Z
- https://api.deps.dev/v3/projects/github.com%2Fchrisdickinson%2Fgit-fetch-pack — retrieved 2026-10-29T18:35:22.580Z
- https://api.deps.dev/v3/systems/npm/packages/git-fetch-pack/versions/0.0.2 — retrieved 2026-10-29T21:28:17.290Z
- https://api.deps.dev/v3/systems/npm/packages/git-fetch-pack/versions/0.0.2:dependencies — retrieved 2026-10-29T21:28:17.310Z