Vulnerability Database · npm · Package report

@aws/lsp-codewhisperer: vulnerability history, versions and safety

@aws/lsp-codewhisperer is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 104 releases, first recorded in Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 24 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @aws/lsp-codewhisperer 0.0.132 i

Updated on 23 Oct 2026

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

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 0.0.132 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 24 Sep 2026 i
  • Highest CVSS 8.5 i
  • With no published fix 0 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 @aws/lsp-codewhisperer, 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
0.0.132 22 Oct 2026 none Apache-2.0 — Details →
0.0.131 15 Oct 2026 none Apache-2.0 — Details →
0.0.130 08 Oct 2026 none Apache-2.0 — Details →
0.0.129 01 Oct 2026 none Apache-2.0 — Details →
0.0.128 09 Sep 2026 none Apache-2.0 — Details →
0.0.127 25 Aug 2026 none Apache-2.0 — Details →
0.0.126 20 Aug 2026 none Apache-2.0 — Details →
0.0.125 18 Aug 2026 none Apache-2.0 — Details →
0.0.124 13 Aug 2026 none Apache-2.0 — Details →
0.0.123 23 Jul 2026 none Apache-2.0 — Details →
0.0.122 09 Jul 2026 none Apache-2.0 — Details →
0.0.121 02 Jul 2026 none Apache-2.0 — Details →
0.0.120 30 Jun 2026 none Apache-2.0 — Details →
0.0.119 09 Jun 2026 none Apache-2.0 — Details →
0.0.118 28 May 2026 none Apache-2.0 — Details →
0.0.117 26 May 2026 none Apache-2.0 — Details →
0.0.116 18 May 2026 H1 Apache-2.0 Yes Details →
0.0.115 13 May 2026 H1 Apache-2.0 Yes Details →
0.0.114 05 May 2026 H1 Apache-2.0 Yes Details →
0.0.113 29 Apr 2026 H1 Apache-2.0 Yes Details →
0.0.112 07 Apr 2026 H2 Apache-2.0 Yes Details →
0.0.111 01 Apr 2026 H2 Apache-2.0 Yes Details →
0.0.110 17 Mar 2026 H2 Apache-2.0 Yes Details →
0.0.109 10 Mar 2026 H2 Apache-2.0 Yes Details →
0.0.108 04 Mar 2026 H2 Apache-2.0 Yes Details →
0.0.107 20 Feb 2026 H2 Apache-2.0 Yes Details →
0.0.106 17 Feb 2026 H2 Apache-2.0 Yes Details →
0.0.105 10 Feb 2026 H2 Apache-2.0 Yes Details →
0.0.104 05 Feb 2026 H2 Apache-2.0 Yes Details →
0.0.103 26 Jan 2026 H2 Apache-2.0 Yes Details →
0.0.102 13 Jan 2026 H2 Apache-2.0 Yes Details →
0.0.101 09 Jan 2026 H2 Apache-2.0 Yes Details →
0.0.100 07 Jan 2026 H2 Apache-2.0 Yes Details →
0.0.99 19 Dec 2025 H2 Apache-2.0 Yes Details →
0.0.98 17 Dec 2025 H2 Apache-2.0 Yes Details →
0.0.97 08 Dec 2025 H2 Apache-2.0 Yes Details →
0.0.96 01 Dec 2025 H2 Apache-2.0 Yes Details →
0.0.95 26 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.94 25 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.93 21 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.92 21 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.90 13 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.89 12 Nov 2025 H2 Apache-2.0 Yes Details →
0.0.88 28 Oct 2025 H2 Apache-2.0 Yes Details →
0.0.86 15 Oct 2025 H2 Apache-2.0 Yes Details →
0.0.85 14 Oct 2025 H2 Apache-2.0 Yes Details →
0.0.84 09 Oct 2025 H2 Apache-2.0 Yes Details →
0.0.83 01 Oct 2025 H2 Apache-2.0 Yes Details →
0.0.82 24 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.81 22 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.80 16 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.79 10 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.78 09 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.77 03 Sep 2025 H2 Apache-2.0 Yes Details →
0.0.76 27 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.75 21 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.74 20 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.73 11 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.72 06 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.71 04 Aug 2025 H2 Apache-2.0 Yes Details →
0.0.70 29 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.69 23 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.68 22 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.67 22 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.66 17 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.65 15 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.64 11 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.63 09 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.62 02 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.61 02 Jul 2025 H2 Apache-2.0 Yes Details →
0.0.60 30 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.59 26 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.58 23 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.57 20 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.56 19 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.55 19 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.54 19 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.53 18 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.52 18 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.51 17 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.50 16 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.49 13 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.48 12 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.47 11 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.46 11 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.45 10 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.44 05 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.43 04 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.42 02 Jun 2025 H2 Apache-2.0 Yes Details →
0.0.41 30 May 2025 H2 Apache-2.0 Yes Details →
0.0.40 22 May 2025 H2 Apache-2.0 Yes Details →
0.0.39 14 May 2025 H2 Apache-2.0 Yes Details →
0.0.38 14 May 2025 H2 Apache-2.0 Yes Details →
0.0.37 09 May 2025 H2 Apache-2.0 Yes Details →
0.0.36 07 May 2025 H2 Apache-2.0 Yes Details →
0.0.35 06 May 2025 H2 Apache-2.0 Yes Details →
0.0.34 02 May 2025 H2 Apache-2.0 Yes Details →
0.0.33 01 May 2025 H2 Apache-2.0 Yes Details →
0.0.32 08 Apr 2025 H2 Apache-2.0 Yes Details →
0.0.31 07 Apr 2025 H2 Apache-2.0 Yes Details →
0.0.30 27 Mar 2025 H2 — Yes Details →
0.0.29 26 Mar 2025 H2 — Yes Details →
0.0.28 19 Mar 2025 H2 — Yes Details →
0.0.27 20 Feb 2025 H2 — Yes Details →
0.0.26 03 Feb 2025 H2 — Yes Details →
0.0.25 28 Jan 2025 H2 — Yes Details →
0.0.24 28 Jan 2025 H2 — Yes Details →
0.0.21 16 Jan 2025 H2 — Yes Details →
0.0.20 15 Jan 2025 H2 — Yes Details →
0.0.19 08 Jan 2025 H2 — Yes Details →
0.0.18 20 Nov 2024 H2 — Yes Details →
0.0.17 13 Nov 2024 H2 — Yes Details →
0.0.16 16 Oct 2024 H2 — Yes Details →
0.0.15 09 Oct 2024 H2 — Yes Details →
0.0.14 13 Sep 2024 H2 — Yes Details →
0.0.13 02 Sep 2024 H2 — Yes Details →
0.0.12 19 Aug 2024 H2 — Yes Details →
0.0.11 15 Aug 2024 H2 — Yes Details →
0.0.10 29 Jul 2024 H2 — Yes Details →
0.0.9 03 Jul 2024 H2 — Yes Details →

The newest 120 of 124 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for @aws/lsp-codewhisperer

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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 @aws/lsp-codewhisperer

Is @aws/lsp-codewhisperer safe to use?

Vulert records 2 vulnerabilities for @aws/lsp-codewhisperer in npm: 0 critical, 2 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 @aws/lsp-codewhisperer's Vulert package health score?

Vulert scores @aws/lsp-codewhisperer 88/100, which reads as healthy. 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 @aws/lsp-codewhisperer affected?

No. 0.0.132, 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.

How many vulnerabilities does @aws/lsp-codewhisperer have?

2 vulnerabilities are recorded for @aws/lsp-codewhisperer in the npm ecosystem: 0 critical, 2 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 @aws/lsp-codewhisperer vulnerabilities disclosed?

2 vulnerabilities were recorded for @aws/lsp-codewhisperer in the last 12 months, and the oldest entry in this database dates to 24 Sep 2026. 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 @aws/lsp-codewhisperer 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 @aws/lsp-codewhisperer for upcoming vulnerabilities?

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