</>PackageGraphPackageGraph

cookie-signature

npmv1.2.2

Sign and unsign cookies

Adopt with care

cookie-signature is usable, with caveats. Last published 680 days ago.

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

    No download data reported for this package yet.

  • CMaintenance: grade C, Fair — worth a look.

    Last published 680 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 4.9 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-signature to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

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

4.9 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

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

Quick start

A usage example from the cookie-signature README.

jsFull README ↗
var cookie = require('cookie-signature');

var val = cookie.sign('hello', 'tobiiscool');
val.should.equal('hello.DGDUkGlIkCzPz+C0B064FNgHdEjox7ch8tOBGslZ5QI');

var val = cookie.sign('hello', 'tobiiscool');
cookie.unsign(val, 'tobiiscool').should.equal('hello');
cookie.unsign(val, 'luna').should.be.false;

cookie-signature vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
cookie-signaturethis page01MIT1 year ago
set-cookie-parser50.2M2MIT1 day ago
cookie05MIT1 day ago
jose02MIT1 day ago

Dependencies

Declared by cookie-signature v1.2.2. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (2)

mocha *should *

Used by

Popular packages that depend on cookie-signature.

expressnpm

Fast, unopinionated, minimalist web framework

↓ 92.8M/wk◈ 17 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of cookie-signature.

expresscookie-signature
cookie-signature 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
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
encodeurlnpm

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

↓ 133.6M/wk◈ 5 dependents⚖ MIT
finalhandlernpm

Node.js final http responder

↓ 132.1M/wk◈ 3 dependents⚖ MIT
type-isnpm

Infer the content-type of a request.

↓ 130.9M/wk◈ 3 dependents⚖ MIT
sendnpm

Better streaming static file server with Range and conditional-GET support

↓ 127.6M/wk◈ 3 dependents⚖ MIT
merge-descriptorsnpm

Merge objects using their property descriptors

↓ 113M/wk◈ 1 dependents⚖ MITTS
oncenpm

Run a function exactly one time

↓ 109.6M/wk◈ 1 dependents⚖ ISC
depdnpm

Deprecate all the things

↓ 103.8M/wk◈ 4 dependents⚖ MIT
varynpm

Manipulate the HTTP Vary header

↓ 100.2M/wk◈ 4 dependents⚖ MIT

Release history

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

Recent versions of cookie-signature
VersionPublishedSizeLicense
1.2.2latest1 year ago4.9 KBMIT
1.0.73 years ago4.0 KBMIT
1.2.13 years ago4.6 KBMIT
1.2.04 years ago4.2 KBMIT
1.1.08 years ago—MIT
1.0.611 years ago—MIT
1.0.512 years ago—MIT
1.0.412 years ago—MIT
1.0.312 years ago—MIT
1.0.212 years ago—MIT
1.0.113 years ago—MIT
1.0.013 years ago—MIT
0.0.114 years ago—MIT

Overview

cookie-signature is an npm package that sign and unsign cookies. It has 1 known dependents in the graph. The latest version is 1.2.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need sign and unsign cookies 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).
  • Lean dependency tree (2 direct dependencies).

Cons

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

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

Maintainers

dougwilsonnatevwtjholowaychuk

Keywords

cookiesignunsign

Frequently asked questions

Should I use cookie-signature?

cookie-signature is usable, with caveats. Last published 680 days ago.

How do I install cookie-signature?

Run `npm install cookie-signature` to add cookie-signature to your npm project.

What license is cookie-signature released under?

cookie-signature is distributed under the MIT license.

How popular is cookie-signature?

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

Is cookie-signature still maintained?

The most recent release of cookie-signature (v1.2.2) was published 1 year ago.

Does cookie-signature run install scripts?

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