cookie
npmv2.0.1HTTP server cookie parsing and serialization
Safe to adopt
Yes — cookie scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 71 days ago. 10 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 71 days ago. 10 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 59 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 3 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 cookie to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=22
- Module format
- ESM only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the cookie README.
import * as cookie from "cookie";cookie vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| cookiethis page | 0 | 5 | MIT | 2 months ago |
| set-cookie-parser | 50.2M | 2 | MIT | 1 day ago |
| cookie-signature | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by cookie v2.0.1. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (8)
Used by
Popular packages that depend on cookie.
Fast, unopinionated, minimalist web framework
UI for Vitest
Fake HTTP injection library
The realtime engine behind Socket.IO. Provides the foundation of a bidirectional connection between client and server
Seamless REST/GraphQL API mocking library for browser and Node.js.
Relationship graph
Dependencies (left) and dependents (right) of cookie.
Frequently installed together
TypeScript definitions for node
Higher-level content negotiation
Lightweight debugging utility for Node.js and the browser
An HTTP/1.1 client, written from scratch for Node.js
An AST-based pattern checker for JavaScript.
Fast, unopinionated, minimalist web framework
Next generation testing framework powered by Vite
Node.js CORS middleware
TypeScript definitions for ws
HTTP status utility
TypeScript definitions for cors
Parser for the client for the realtime Engine
Release history
4 releases in the last two years, typically about 40 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.1latest | 2 months ago | 59 KB | MIT |
| 2.0.0 | 2 months ago | 59 KB | MIT |
| 1.1.1 | 9 months ago | 59 KB | MIT |
| 1.1.0 | 9 months ago | 59 KB | MIT |
| 1.0.2 | 1 year ago | 45 KB | MIT |
| 1.0.1 | 1 year ago | 45 KB | MIT |
| 1.0.0 | 1 year ago | 44 KB | MIT |
| 0.7.2 | 1 year ago | 23 KB | MIT |
| 0.7.1 | 1 year ago | 23 KB | MIT |
| 0.7.0 | 1 year ago | 23 KB | MIT |
| 0.6.0 | 2 years ago | 23 KB | MIT |
| 0.5.0 | 4 years ago | 23 KB | MIT |
| 0.4.2 | 4 years ago | 19 KB | MIT |
| 0.4.1 | 6 years ago | 18 KB | MIT |
| 0.4.0 | 7 years ago | 17 KB | MIT |
Overview
cookie is an npm package that hTTP server cookie parsing and serialization. It has 5 known dependents in the graph. The latest version is 2.0.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need hTTP server cookie parsing and serialization 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
Funding
Frequently asked questions
Should I use cookie?
Yes — cookie scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 71 days ago. 10 releases in the last 2 years.
How do I install cookie?
Run `npm install cookie` to add cookie to your npm project.
What license is cookie released under?
cookie is distributed under the MIT license.
How popular is cookie?
npm does not publish download counts. Within PackageGraph's crawl, 5 known packages depend on cookie.
Is cookie still maintained?
The most recent release of cookie (v2.0.1) was published 2 months ago.
Does cookie run install scripts?
No. cookie does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.