send
npmv1.2.1Better streaming static file server with Range and conditional-GET support
Safe to adopt
Yes — send scores well across adoption, maintenance, weight, supply chain, and licensing. 143.3M downloads per week and 3 known dependents. Last published 268 days ago. 6 releases in the last 2 years.
- AAdoption: grade A, Excellent.
143.3M downloads per week and 3 known dependents.
- BMaintenance: grade B, Good.
Last published 268 days ago. 6 releases in the last 2 years.
- BWeight: grade B, Good.
Pulls in 17 transitive packages, about 421 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 4 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 send 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.
Licenses in the dependency tree
Every license you inherit by installing send, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >= 18
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the send README.
var send = require('send')send 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 |
|---|---|---|---|---|
| sendthis page | 143.3M | 3 | MIT | 8 months ago |
| locate-path | 318.2M | 1 | MIT | 9 days ago |
| callsites | 157.5M | 1 | MIT | 9 days ago |
| open | 144.2M | 4 | MIT | 8 days ago |
| normalize-path | 139.7M | 1 | MIT | 9 days ago |
| anymatch | 116.4M | 1 | ISC | 9 days ago |
Dependencies
Declared by send v1.2.1. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (11)
Dev (11)
Used by
Popular packages that depend on send.
Relationship graph
Dependencies (left) and dependents (right) of send.
Frequently installed together
The Expo SDK
Expo Router is a file-based router for React Native and web applications.
Lightweight debugging utility for Node.js and the browser
Higher-level content negotiation
TypeScript-first schema declaration and validation library with static type inference
Get details about the current Continuous Integration environment
Unopinionated, no-frills CLI argument parser
A high-level API to automate web browsers
JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Create clickable links in the terminal
A framework for building native apps using React
A library for interacting with the app.json
Release history
3 releases in the last two years, typically about 47 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.2.1latest | 8 months ago | 31 KB | MIT |
| 0.19.2 | 8 months ago | 49 KB | MIT |
| 1.2.0 | 1 year ago | 46 KB | MIT |
| 0.19.1 | 1 year ago | 49 KB | MIT |
| 1.1.0 | 2 years ago | 47 KB | MIT |
| 0.19.0 | 2 years ago | 49 KB | MIT |
| 1.0.0 | 2 years ago | 47 KB | MIT |
| 1.0.0-beta.2 | 2 years ago | 47 KB | MIT |
| 0.18.0 | 4 years ago | 49 KB | MIT |
| 1.0.0-beta.1 | 4 years ago | 45 KB | MIT |
| 0.17.2 | 4 years ago | 47 KB | MIT |
| 0.17.1 | 7 years ago | 47 KB | MIT |
| 0.17.0 | 7 years ago | 47 KB | MIT |
| 0.16.2 | 8 years ago | 45 KB | MIT |
| 0.16.1 | 9 years ago | — | MIT |
Overview
send is an npm package that better streaming static file server with Range and conditional-GET support. It is extremely widely used, with about 143.3M downloads per week and 3 known dependents in the graph. The latest version is 1.2.1, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need better streaming static file server with Range and conditional-GET support and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to minimize your dependency tree, 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 (143.3M weekly downloads).
- Clear open-source license (MIT).
Cons
- Large dependency tree (22 direct dependencies) increases install size and audit surface.
- 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 send?
Yes — send scores well across adoption, maintenance, weight, supply chain, and licensing. 143.3M downloads per week and 3 known dependents. Last published 268 days ago. 6 releases in the last 2 years.
How do I install send?
Run `npm install send` to add send to your npm project.
How many dependencies does send have?
send declares 22 direct dependencies and pulls in 17 packages in total once its runtime tree is resolved totalling about 421 KB on disk.
What license is send released under?
send is distributed under the MIT license. Its dependency tree also includes: ISC, MIT.
How popular is send?
send has approximately 143,260,992 downloads per week and 3 known dependent packages.
Is send still maintained?
The most recent release of send (v1.2.1) was published 8 months ago.
Does send run install scripts?
No. send does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.