contentful-resolve-response 1.1.1

[![Build Status](https://travis-ci.org/contentful/contentful-resolve-response.svg?branch=master)](https://travis-ci.org/contentful/contentful-resolve-response) [![codecov](https://codecov.io/gh/contentful/contentful-resolve-response/branch/master/graph/ba

contentful-resolve-response@1.1.1 was published on 2018-01-29. Its manifest declares 1 runtime dependency 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 contentful-resolve-response versions · Permanent reference to 1.1.1 · View npm registry JSON · Latest release

Package specifications

Version1.1.1
License declarationMIT
Published2018-01-29T09:40:06.442Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution sizeNot supplied
Published file countNot supplied
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars57
Repository forks13

Install contentful-resolve-response 1.1.1

npm install contentful-resolve-response@1.1.1
pnpm add contentful-resolve-response@1.1.1
yarn add contentful-resolve-response@1.1.1

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.

OpenSSF repository checks

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

Maintained10/10 — 28 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review5/10 — Found 3/6 approved changesets -- score normalized to 5
Binary-Artifacts10/10 — no binaries found in the repo
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
Token-Permissions8/10 — detected GitHub workflow tokens with excessive permissions
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Security-Policy10/10 — security policy file detected
Branch-Protection4/10 — branch protection is not maximal on development and all release branches
SAST10/10 — SAST tool is run on all commits

Evidence and freshness