</>PackageGraphPackageGraph

cookies

npmv0.9.1

Cookies, optionally signed using Keygrip.

Adopt with care

cookies is usable, with caveats. Last published 982 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • DMaintenance: grade D, Poor — a real concern.

    Last published 982 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 3 transitive packages, about 64 KB installed.

  • ASupply chain: grade A, Excellent.

    No install scripts, 2 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding cookies to a project.

2
Direct dependencies

Runtime packages this one declares itself.

3
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

64 KB
Install size

Unpacked size of this package plus its entire runtime tree.

2
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing cookies, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 0.8
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the cookies README.

jsFull README ↗
var http = require('http')
var Cookies = require('cookies')

// Optionally define keys to sign cookie values
// to prevent client tampering
var keys = ['keyboard cat']

var server = http.createServer(function (req, res) {
  // Create a cookies object
  var cookies = new Cookies(req, res, { keys: keys })

  // Get a cookie
  var lastVisit = cookies.get('LastVisit', { signed: true })
Example truncated — see the full README.

Dependencies

Declared by cookies v0.9.1. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (2)

depd ~2.0.0keygrip ~1.1.0

Dev (6)

eslint 8.56.0express 4.18.2mocha 10.2.0nyc 15.1.0restify 8.6.1supertest 6.3.3

Used by

Popular packages that depend on cookies.

koanpm

Koa web app framework

↓ 6.8M/wk◈ 0 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of cookies.

depdkeygripkoacookies
cookies dependencies dependents

Frequently installed together

content-typenpm

Create and parse HTTP Content-Type header

↓ 191.4M/wk◈ 6 dependents⚖ MITTS
mime-typesnpm

The ultimate javascript content-type utility.

↓ 185.3M/wk◈ 9 dependents⚖ MIT
http-errorsnpm

Create HTTP error objects

↓ 149.4M/wk◈ 7 dependents⚖ MIT
encodeurlnpm

Encode a URL to a percent-encoded form, excluding already-encoded sequences

↓ 133.6M/wk◈ 5 dependents⚖ MIT
type-isnpm

Infer the content-type of a request.

↓ 130.9M/wk◈ 3 dependents⚖ MIT
varynpm

Manipulate the HTTP Vary header

↓ 100.2M/wk◈ 4 dependents⚖ MIT
on-finishednpm

Execute a callback when a request closes, finishes, or errors

↓ 96.7M/wk◈ 5 dependents⚖ MIT
koa-composenpm

compose Koa middleware

↓ 0/wk◈ 1 dependents⚖ MIT
content-dispositionnpm

Create and parse Content-Disposition header

↓ 0/wk◈ 2 dependents⚖ MITTS
delegatesnpm

delegate methods and accessors to another property

↓ 0/wk◈ 1 dependents⚖ MIT
freshnpm

HTTP response freshness testing

↓ 0/wk◈ 3 dependents⚖ MIT
acceptsnpm

Higher-level content negotiation

↓ 0/wk◈ 7 dependents⚖ MIT

Release history

No releases in the last two years, typically about 96 days apart.

Recent versions of cookies
VersionPublishedSizeLicense
0.9.1latest2 years ago22 KBMIT
0.9.02 years ago22 KBMIT
0.8.07 years ago19 KBMIT
0.7.37 years ago19 KBMIT
0.7.28 years ago19 KBMIT
0.7.19 years ago—MIT
0.7.09 years ago—MIT
0.6.29 years ago—MIT
0.6.110 years ago—MIT
0.6.010 years ago—MIT
0.5.111 years ago—MIT
0.5.012 years ago—MIT
0.4.112 years ago—MIT
0.4.012 years ago—MIT
0.3.812 years ago—MIT

Overview

cookies is an npm package that cookies, optionally signed using Keygrip. It has 1 known dependents in the graph. The latest version is 0.9.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need cookies, optionally signed using Keygrip and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

dougwilsonjongleberry

Frequently asked questions

Should I use cookies?

cookies is usable, with caveats. Last published 982 days ago.

How do I install cookies?

Run `npm install cookies` to add cookies to your npm project.

How many dependencies does cookies have?

cookies declares 8 direct dependencies and pulls in 3 packages in total once its runtime tree is resolved totalling about 64 KB on disk.

What license is cookies released under?

cookies is distributed under the MIT license.

How popular is cookies?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on cookies.

Is cookies still maintained?

The most recent release of cookies (v0.9.1) was published 2 years ago.

Does cookies run install scripts?

No. cookies does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.