npm package
send 1.2.1: no known vulnerabilities
send 1.2.1 has no known vulnerabilities in OSV.dev.
npm (opens in a new tab) describes it as “Better streaming static file server with Range and conditional-GET support”
- Known vulnerabilities
- 0
- None in OSV.dev
- Released
- Dec 15, 2025
- The latest release
- Downloads last week
- 69M
- 45% of send downloads
- Licence
- MIT
- Pulls in
- 17 packages
- Resolved by deps.dev
Newer releases
1.2.1 is the latest release of send.
Who is still on a vulnerable send
7% of last week’s 153.5M send downloads went to versions with known vulnerabilities.
From npm’s per-version download counts for the last 7 days, each version checked against OSV.dev. The versions checked cover over 99% of downloads.
Is send the only one?
Paste a public GitHub repo or drop your package.json and see every vulnerable, end-of-life or deprecated dependency, with one fix task. Free, no sign-up.
How this page is checked
StackPrism asks OSV.dev which advisories affect exactly send 1.2.1, merges duplicates filed under several ids, and ranks them with CISA’s Known Exploited Vulnerabilities list and FIRST EPSS. Release dates and deprecation come from deps.dev and npm. No AI writes this page: every sentence comes from that data, refreshed every few hours.