Is got healthy, maintained, and safe?
Mostly yes — got is maintained, with a couple of watch-items rather than red flags.
The verdict
OSPulse scores got at 77/100 (low risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. Mostly yes — got is maintained, with a couple of watch-items rather than red flags.
Its most recent release shipped on 2 July 2026 — 25 days ago — so development is clearly active. Across 202 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. Ownership rests on a single maintainer — a bus-factor of one, meaning one person's availability is a single point of failure for everyone downstream.
OSV lists 1 known advisory for got, of assorted severity. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
A couple of watch-items aside, got is a reasonable dependency to rely on; keep an eye on the flagged signals. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (1)
Got allows a redirect to a UNIX socket
Key facts
- Latest version
- v15.1.0
- Last release
- 2 July 2026 (25 days ago)
- Total releases
- 202
- First release
- 27 March 2014
- Package age
- 12.3 years
- Maintainers
- 1
- Known advisories
- 1
- Confidence
- High
Frequently asked
Is got still maintained?
Yes — got released as recently as 2 July 2026 (25 days ago), so it is actively maintained.
Does got have known security vulnerabilities?
Yes — OSV lists 1 advisory for got. See the advisory list on this page for the OSV/GHSA identifiers.
Is got safe to use?
Mostly yes — got is maintained, with a couple of watch-items rather than red flags. OSPulse rates it 77/100 (low risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
got is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.