npm-registry-fetch 1.1.0

Fetch-based http client for use with npm registry APIs

npm-registry-fetch@1.1.0 was published on 2018-03-16. Its manifest declares 6 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 npm-registry-fetch versions · Permanent reference to 1.1.0 · Latest release

Package specifications

Version1.1.0
License declarationISC
Published2018-03-16T21:50:43.198Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size33.28 KiB
Published file count10
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies93
Repository stars161
Repository forks45

Install npm-registry-fetch 1.1.0

npm install npm-registry-fetch@1.1.0
pnpm add npm-registry-fetch@1.1.0
yarn add npm-registry-fetch@1.1.0

Runtime dependencies

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.

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.

Known direct advisories

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Maintained2/10 — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Code-Review10/10 — all changesets reviewed
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Security-Policy10/10 — security policy file detected
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
License9/10 — license file detected
Fuzzing0/10 — project is not fuzzed
SAST9/10 — SAST tool detected but not run on all commits

Evidence and freshness