VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/dop251/goja_nodejs: vulnerability history, versions and safety

github.com/dop251/goja_nodejs is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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 github.com/dop251/goja_nodejs vulnerabilities

Vulert verdict on github.com/dop251/goja_nodejs v0.0.0-20260212111938-1f56ff5bcf14 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260212111938-1f56ff5bcf14, the version you would install today, has no known vulnerabilities.

Package health score 70/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20260212111938-1f56ff5bcf14 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 443 i
  • OpenSSF scorecard 3/10 i
  • Last release 8 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/dop251/goja_nodejs, 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
v0.0.0-20260918173711-b481721df8a2 18 Sep 2026 none MIT — Details →
v0.0.0-20260212111938-1f56ff5bcf14 12 Feb 2026 none MIT — Details →
v0.0.0-20251015164255-5e94316bedaf 15 Oct 2025 none MIT — Details →
v0.0.0-20251015150807-de3cef52e0fb 15 Oct 2025 none MIT — Details →
v0.0.0-20250409162600-f7acab6894b0 09 Apr 2025 none MIT — Details →
v0.0.0-20250325151027-56d2092bee9a 25 Mar 2025 none MIT — Details →
v0.0.0-20250314160716-c55ecee183c0 14 Mar 2025 none MIT — Details →
v0.0.0-20250313154628-ba888e424a3a 13 Mar 2025 none MIT — Details →
v0.0.0-20250309172600-86a40d630cdd 09 Mar 2025 none MIT — Details →
v0.0.0-20250306164425-a0199362a3ae 06 Mar 2025 none MIT — Details →
v0.0.0-20250305231445-42bc4c0864aa 05 Mar 2025 none MIT — Details →
v0.0.0-20250302133430-0ba139dfda9a 02 Mar 2025 none MIT — Details →
v0.0.0-20250217171036-ba90ff8d8790 17 Feb 2025 none MIT — Details →
v0.0.0-20250211202206-2ae4cd213512 11 Feb 2025 none MIT — Details →
v0.0.0-20240728170619-29b559befffc 28 Jul 2024 none MIT — Details →
v0.0.0-20240728170227-6a689e9e1d06 28 Jul 2024 none MIT — Details →
v0.0.0-20240726172143-acd17a06564a 26 Jul 2024 none MIT — Details →
v0.0.0-20240418154818-2aae10d4cbcf 18 Apr 2024 none MIT — Details →
v0.0.0-20240221231712-27eeffc9c235 21 Feb 2024 none MIT — Details →
v0.0.0-20240221224457-e1b638b8df04 21 Feb 2024 none MIT — Details →
v0.0.0-20231122114759-e84d9a924c5c 22 Nov 2023 none MIT — Details →
v0.0.0-20231122072438-4d13b2f53bde 22 Nov 2023 none MIT — Details →
v0.0.0-20231022114343-5c1f9037c9ab 22 Oct 2023 none MIT — Details →
v0.0.0-20231022113835-95dd0792c0c0 22 Oct 2023 none MIT — Details →
v0.0.0-20230914102007-198ba9a8b098 14 Sep 2023 none MIT — Details →
v0.0.0-20230913203144-171fa94d75f5 13 Sep 2023 none MIT — Details →
v0.0.0-20230821135201-94e508132562 21 Aug 2023 none MIT — Details →
v0.0.0-20230731184339-9ba67d720a81 31 Jul 2023 none MIT — Details →
v0.0.0-20230727164059-07887644b3d4 27 Jul 2023 none MIT — Details →
v0.0.0-20230602164024-804a84515562 02 Jun 2023 none MIT — Details →
v0.0.0-20230322100729-2550c7b6c124 22 Mar 2023 none MIT — Details →
v0.0.0-20230320130059-dcf93ba651dd 20 Mar 2023 none MIT — Details →
v0.0.0-20230226152057-060fa99b809f 26 Feb 2023 none MIT — Details →
v0.0.0-20230222172725-12ac04f8c000 22 Feb 2023 none MIT — Details →
v0.0.0-20230207183254-2229640ea097 07 Feb 2023 none MIT — Details →
v0.0.0-20230121151440-041f29a15066 21 Jan 2023 none MIT — Details →
v0.0.0-20230121151348-7ebd95c712e9 21 Jan 2023 none MIT — Details →
v0.0.0-20221211191749-434192f0843e 11 Dec 2022 none MIT — Details →
v0.0.0-20221009164102-3aa5028e57f6 09 Oct 2022 none MIT — Details →
v0.0.0-20221009162119-5d6ef6ec32aa 09 Oct 2022 none MIT — Details →
v0.0.0-20220905124449-678b33ca5009 05 Sep 2022 none MIT — Details →
v0.0.0-20220905121206-287d3f317fa7 05 Sep 2022 none MIT — Details →
v0.0.0-20220831121936-6b39750d7639 31 Aug 2022 none MIT — Details →
v0.0.0-20220808115320-bac29516aae9 08 Aug 2022 none MIT — Details →
v0.0.0-20220806163711-ca17575a9f4f 06 Aug 2022 none MIT — Details →
v0.0.0-20220806162759-353a00f72fa4 06 Aug 2022 none MIT — Details →
v0.0.0-20220712185256-8cad205bf387 12 Jul 2022 none MIT — Details →
v0.0.0-20220706223936-8bb8eec2f26a 06 Jul 2022 none MIT — Details →
v0.0.0-20220706085836-9625ef2e59cb 06 Jul 2022 none MIT — Details →
v0.0.0-20211022123610-8dd9abb0616d 22 Oct 2021 none MIT — Details →
v0.0.0-20211022123610-bb36e573f42b 22 Oct 2021 none MIT — Details →
v0.0.0-20210920152751-582170a1676b 20 Sep 2021 none MIT — Details →
v0.0.0-20210225215109-d91c329300e7 25 Feb 2021 none MIT — Details →
v0.0.0-20201222133159-1629e8d0b836 22 Dec 2020 none MIT — Details →
v0.0.0-20201219133904-e244704ff7c8 19 Dec 2020 none MIT — Details →
v0.0.0-20201201133918-0226646606a0 01 Dec 2020 none MIT — Details →
v0.0.0-20201201133717-5dc79c9e9ff4 01 Dec 2020 none MIT — Details →
v0.0.0-20200811150831-9bc458b4bbeb 11 Aug 2020 none MIT — Details →
v0.0.0-20200728182148-d8e650e3b24d 28 Jul 2020 none MIT — Details →
v0.0.0-20200727212512-f195c6de9c52 27 Jul 2020 none MIT — Details →
v0.0.0-20200727121546-8b6014989c47 27 Jul 2020 none MIT — Details →
v0.0.0-20200718202923-03d0f618a5eb 18 Jul 2020 none MIT — Details →
v0.0.0-20200706082813-b2775b86b9e0 06 Jul 2020 none MIT — Details →
v0.0.0-20200705212330-ea7a29a57a6d 05 Jul 2020 none MIT — Details →
v0.0.0-20200703190029-532bc92299f1 03 Jul 2020 none MIT — Details →
v0.0.0-20200629185815-2c377ae209ab 29 Jun 2020 none MIT — Details →
v0.0.0-20200629185135-64fe9cf7d8e0 29 Jun 2020 none MIT — Details →
v0.0.0-20200629153519-6963a0a24296 29 Jun 2020 none MIT — Details →
v0.0.0-20200626162143-3e6a054e8447 26 Jun 2020 none MIT — Details →
v0.0.0-20200128125109-2d688c7e0ac4 28 Jan 2020 none MIT — Details →
v0.0.0-20200120171228-34eac44e576f 20 Jan 2020 none MIT — Details →
v0.0.0-20171228135845-804c0ff1e5cf 28 Dec 2017 none MIT — Details →
v0.0.0-20171011081505-adff31b136e6 11 Oct 2017 none MIT — Details →
v0.0.0-20171011034214-cc67fad196bf 11 Oct 2017 none MIT — Details →
v0.0.0-20170413183924-fdfc26f6b65b 13 Apr 2017 none MIT — Details →
v0.0.0-20161230154048-2fc1e6bbfc49 30 Dec 2016 none MIT — Details →
v0.0.0-20161119151243-062d836dd7e5 19 Nov 2016 none MIT — Details →
v0.0.0-20161112104632-91415bfec702 12 Nov 2016 none MIT — Details →
v0.0.0-20161112001343-021b29c111cf 12 Nov 2016 none MIT — Details →
v0.0.0-20161111195613-c108e697924e 11 Nov 2016 none MIT — Details →
v0.0.0-20161111181210-bf0847e1d826 11 Nov 2016 none MIT — Details →

All 81 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.

03 Vulnerabilities

Recorded vulnerabilities for github.com/dop251/goja_nodejs

No vulnerability write-ups match this view

Search all 0 in the database →

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 github.com/dop251/goja_nodejs

Is github.com/dop251/goja_nodejs safe to use?

Vulert has no vulnerabilities on record for github.com/dop251/goja_nodejs in Go 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 github.com/dop251/goja_nodejs's Vulert package health score?

Vulert scores github.com/dop251/goja_nodejs 70/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 github.com/dop251/goja_nodejs affected?

No. v0.0.0-20260212111938-1f56ff5bcf14, 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 github.com/dop251/goja_nodejs should I use?

v0.0.0-20260212111938-1f56ff5bcf14 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 github.com/dop251/goja_nodejs have?

0 vulnerabilities are recorded for github.com/dop251/goja_nodejs in the Go 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 github.com/dop251/goja_nodejs vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/dop251/goja_nodejs 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 github.com/dop251/goja_nodejs 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 github.com/dop251/goja_nodejs for upcoming vulnerabilities?

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