</>PackageGraphPackageGraph

vary

npmv1.1.2

Manipulate the HTTP Vary header

Not recommended for new projects

No — vary should not be adopted for new projects. Last published 3273 days ago.

  • AAdoption: grade A, Excellent.

    100.2M downloads per week and 4 known dependents.

  • FMaintenance: grade F, Failing.

    Last published 3273 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • 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 vary 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.

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 >= 0.8
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the vary README.

var vary = require('vary')

vary vs the alternatives

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

PackageWeekly downloadsDependentsLicenseLast release
varythis page100.2M4MIT9 years ago
content-type191.4M6MIT1 day ago
etag100M4MIT1 day ago
content-disposition02MIT1 day ago
negotiator183.3M2MIT1 day ago
node-fetch172.9M9MIT1 day ago

Dependencies

Declared by vary v1.1.2. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (12)

beautify-benchmark 0.2.4benchmark 2.1.4eslint 3.19.0eslint-config-standard 10.2.1eslint-plugin-import 2.7.0eslint-plugin-markdown 1.0.0-beta.6eslint-plugin-node 5.1.1eslint-plugin-promise 3.5.0eslint-plugin-standard 3.0.1istanbul 0.4.5mocha 2.5.3supertest 1.1.0

Used by

Popular packages that depend on vary.

Relationship graph

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

expresscorsfastifykoavary
vary dependencies dependents

Frequently installed together

Release history

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

Recent versions of vary
VersionPublishedSizeLicense
1.1.2latest9 years agoMIT
1.1.19 years agoMIT
1.1.011 years agoMIT
1.0.111 years agoMIT
1.0.012 years agoMIT
0.1.012 years agoMIT
0.0.012 years agoMIT

Overview

vary is an npm package that manipulate the HTTP Vary header. It is extremely widely used, with about 100.2M downloads per week and 4 known dependents in the graph. The latest version is 1.1.2, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need manipulate the HTTP Vary header and value a battle-tested, widely-adopted 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

  • Large, well-established user base (100.2M weekly downloads).
  • 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

Keywords

Frequently asked questions

Should I use vary?

No — vary should not be adopted for new projects. Last published 3273 days ago.

How do I install vary?

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

What license is vary released under?

vary is distributed under the MIT license.

How popular is vary?

vary has approximately 100,162,905 downloads per week and 4 known dependent packages.

Is vary still maintained?

The most recent release of vary (v1.1.2) was published 9 years ago.

Does vary run install scripts?

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