Vulnerability Database · npm · Package report

langium: vulnerability history, versions and safety

Q: How do I monitor langium for upcoming vulnerabilities?

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

langium is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all langium vulnerabilities

Vulert verdict on langium 4.4.0 i

Updated on 23 Oct 2026

Good news: 4.4.0, the version you would install today, has no known vulnerabilities.

Package health score 89/100

Security No known security issues
Maintenance Sustainable
Popularity Niche
Community Moderate

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

Current release 4.4.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 71 packages i
Stars 1,043 i
Last release 1 month ago i
Licence MIT 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for langium, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
4.4.0	09 Sep 2026	none	MIT	—	Details →
4.3.1	02 Jul 2026	none	MIT	—	Details →
4.3.0	15 Jun 2026	none	MIT	—	Details →
4.3.0-next.a52b426	08 Jun 2026	none	MIT	—	Details →
4.2.4	11 May 2026	none	MIT	—	Details →
4.2.3	01 May 2026	none	MIT	—	Details →
4.2.2-next.d9c47299	30 Apr 2026	none	MIT	—	Details →
4.2.2	07 Apr 2026	none	MIT	—	Details →
4.2.1	10 Feb 2026	none	MIT	—	Details →
4.2.0	27 Jan 2026	none	MIT	—	Details →
4.1.3	19 Dec 2025	none	MIT	—	Details →
4.1.2	26 Nov 2025	none	MIT	—	Details →
4.1.1	20 Nov 2025	none	MIT	—	Details →
4.1.0	19 Sep 2025	none	MIT	—	Details →
4.0.3	16 Sep 2025	none	MIT	—	Details →
4.0.2	16 Sep 2025	none	MIT	—	Details →
4.0.1	10 Sep 2025	none	MIT	—	Details →
4.0.0	31 Jul 2025	none	MIT	—	Details →
3.5.0-next.91328d6	22 Jul 2025	none	MIT	—	Details →
3.5.0-next.936a9d7	03 Jul 2025	none	MIT	—	Details →
3.5.0	17 Apr 2025	none	MIT	—	Details →
3.4.0-next.89c0a9d	28 Mar 2025	none	MIT	—	Details →
3.4.0-next.10c0eb7	04 Mar 2025	none	MIT	—	Details →
3.4.0	26 Feb 2025	none	MIT	—	Details →
3.3.1	23 Jan 2025	none	MIT	—	Details →
3.4.0-next.325db9f	11 Dec 2024	none	MIT	—	Details →
3.4.0-next.325db9e	11 Dec 2024	none	MIT	—	Details →
3.4.0-next.1409e5d	11 Dec 2024	none	MIT	—	Details →
3.3.0	18 Nov 2024	none	MIT	—	Details →
3.2.1	05 Nov 2024	none	MIT	—	Details →
3.2.0	06 Sep 2024	none	MIT	—	Details →
3.2.0-next.5063a2b	29 Aug 2024	none	MIT	—	Details →
3.1.3	07 Aug 2024	none	MIT	—	Details →
3.1.2	04 Jul 2024	none	MIT	—	Details →
3.2.0-next.bb9f2d3	02 Jul 2024	none	MIT	—	Details →
3.2.0-next.9134e27	02 Jul 2024	none	MIT	—	Details →
3.2.0-next.2191297	01 Jul 2024	none	MIT	—	Details →
3.1.1	24 Jun 2024	none	MIT	—	Details →
3.1.0	20 Jun 2024	none	MIT	—	Details →
3.1.0-next.4bbc180	18 Jun 2024	none	MIT	—	Details →
3.1.0-next.cbc5db3	11 Jun 2024	none	MIT	—	Details →
3.1.0-next.c8e01a2	11 Jun 2024	none	MIT	—	Details →
3.0.0	29 Feb 2024	none	MIT	—	Details →
3.0.0-next.cc1a49c	27 Feb 2024	none	MIT	—	Details →
3.0.0-next.e78aeba	14 Feb 2024	none	MIT	—	Details →
3.0.0-next.79e4301	12 Dec 2023	none	MIT	—	Details →
2.1.3	21 Nov 2023	none	MIT	—	Details →
2.1.2	08 Nov 2023	none	MIT	—	Details →
2.1.1	06 Nov 2023	none	MIT	—	Details →
2.1.0	02 Nov 2023	none	MIT	—	Details →
2.0.2	05 Sep 2023	none	MIT	—	Details →
1.3.1	05 Sep 2023	none	MIT	—	Details →
2.0.1	22 Aug 2023	none	MIT	—	Details →
2.0.0	17 Aug 2023	none	MIT	—	Details →
1.3.0	17 Aug 2023	none	MIT	—	Details →
2.0.0-next.a57102f	08 Aug 2023	none	MIT	—	Details →
2.0.0-next.239179f	25 Jul 2023	none	MIT	—	Details →
1.2.1	22 Jun 2023	none	MIT	—	Details →
1.2.0	02 May 2023	none	MIT	—	Details →
1.1.0	15 Feb 2023	none	MIT	—	Details →
1.0.1	23 Dec 2022	none	MIT	—	Details →
1.0.0	16 Dec 2022	none	MIT	—	Details →
0.6.0-next.62c127c	08 Nov 2022	none	MIT	—	Details →
0.5.0	05 Oct 2022	none	MIT	—	Details →
0.5.0-next.52ab085	16 Sep 2022	none	MIT	—	Details →
0.5.0-next.f150dbd	02 Sep 2022	none	MIT	—	Details →
0.5.0-next.f2b3802	29 Jun 2022	none	MIT	—	Details →
0.4.0	09 Jun 2022	none	MIT	—	Details →
0.3.0	17 Mar 2022	none	MIT	—	Details →
0.3.0-next.ee4fc4e	15 Mar 2022	none	MIT	—	Details →
0.3.0-next.5e9d27d	16 Dec 2021	none	MIT	—	Details →
0.2.0	03 Nov 2021	none	MIT	—	Details →
0.2.0-next.1f60202	18 Oct 2021	none	MIT	—	Details →
0.1.0	24 Jun 2021	none	MIT	—	Details →
0.1.0-next.b687a8a	24 Jun 2021	none	MIT	—	Details →
0.1.0-next.6f45aec	24 Jun 2021	none	MIT	—	Details →
0.1.0-next.0e84185	24 Jun 2021	none	MIT	—	Details →
0.1.0-next.00ebfd9	16 Jun 2021	none	MIT	—	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for langium

No vulnerabilities match this view.

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 langium

Is langium safe to use?

Vulert has no vulnerabilities on record for langium in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is langium's Vulert package health score?

Vulert scores langium 89/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 langium affected?

No. 4.4.0, 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 langium should I use?

4.4.0 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 langium have?

0 vulnerabilities are recorded for langium in the npm ecosystem: 0 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 langium vulnerabilities disclosed?

0 vulnerabilities were recorded for langium in the last 12 months. 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 langium 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 langium for upcoming vulnerabilities?

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