VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@tomphttp/bare-server-node: vulnerability history, versions and safety

@tomphttp/bare-server-node is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 25 releases, first recorded in Mar 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @tomphttp/bare-server-node vulnerabilities

Vulert verdict on @tomphttp/bare-server-node 2.0.6 i

Updated on 23 Oct 2026

Good news: 2.0.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 73/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

What to do: Stay on 2.0.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.0.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.0.6 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Mar 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 75 i
  • Last release 13 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @tomphttp/bare-server-node, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.0.6 23 Sep 2025 none GPL-3.0 — Details →
2.0.5 06 Nov 2024 none GPL-3.0 — Details →
2.0.4 24 Jul 2024 none GPL-3.0 — Details →
2.0.3 08 Mar 2024 none GPL-3.0 — Details →
2.0.2 04 Mar 2024 none GPL-3.0 — Details →
2.0.1 08 Jul 2023 C1 GPL-3.0 Yes Details →
2.0.0 13 Jun 2023 C1 GPL-3.0 Yes Details →
2.0.0-beta 08 Jun 2023 C1 GPL-3.0 Yes Details →
1.2.6 26 May 2023 C1 GPL-3.0 Yes Details →
1.2.5 18 Feb 2023 C1 GPL-3.0 Yes Details →
1.2.4 18 Feb 2023 C1 GPL-3.0 Yes Details →
1.2.3 24 Jan 2023 C1 GPL-3.0 Yes Details →
1.2.2 22 Nov 2022 C1 GPL-3.0 Yes Details →
1.2.1 22 Nov 2022 C1 GPL-3.0 Yes Details →
1.1.0 24 Sep 2022 C1 GPL-3.0 Yes Details →
1.0.4-deps1 16 Sep 2022 C1 GPL-3.0 Yes Details →
1.0.4 16 Sep 2022 C1 GPL-3.0 Yes Details →
1.0.3-deps2 31 Jul 2022 C1 GPL-3.0 Yes Details →
1.0.3-log1 29 Jul 2022 C1 GPL-3.0 Yes Details →
1.0.3 29 Jul 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta-readme5 12 Jul 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta-readme4 02 Jul 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta-typings3 30 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta-readme2 22 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta-rollup1 21 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.2-beta 21 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.1-beta-readme1 21 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.1-beta 21 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.0-beta-readme1 21 Jun 2022 C1 GPL-3.0 Yes Details →
1.0.0-beta 21 Jun 2022 C1 GPL-3.0 Yes Details →

All 30 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @tomphttp/bare-server-node

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
HTTP Handling Vulnerability in @tomphttp/bare-server-node 9.8 critical 2.0.2 05 Mar 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @tomphttp/bare-server-node

Is @tomphttp/bare-server-node safe to use?

Vulert records 1 vulnerabilities for @tomphttp/bare-server-node in npm: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @tomphttp/bare-server-node's Vulert package health score?

Vulert scores @tomphttp/bare-server-node 73/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @tomphttp/bare-server-node affected?

No. 2.0.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @tomphttp/bare-server-node should I use?

2.0.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @tomphttp/bare-server-node have?

1 vulnerability is recorded for @tomphttp/bare-server-node in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @tomphttp/bare-server-node vulnerabilities disclosed?

0 vulnerabilities were recorded for @tomphttp/bare-server-node in the last 12 months, and the oldest entry in this database dates to 05 Mar 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @tomphttp/bare-server-node are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @tomphttp/bare-server-node for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @tomphttp/bare-server-node version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.