VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/di-wu/parser: vulnerability history, versions and safety

github.com/di-wu/parser 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/di-wu/parser vulnerabilities

Vulert verdict on github.com/di-wu/parser v0.3.0 i

Updated on 23 Oct 2026

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

Package health score 44/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3 i
  • OpenSSF scorecard 2/10 i
  • Last release 64 months ago i
  • Licence Apache-2.0 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/di-wu/parser, 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.3.1-0.20220225222249-1da5d88dd204 25 Feb 2022 none Apache-2.0 — Details →
v0.3.1-0.20210602171053-94d72f8aa61c 02 Jun 2021 none Apache-2.0 — Details →
v0.3.0 02 Jun 2021 none Apache-2.0 — Details →
v0.2.2 09 Mar 2021 none Apache-2.0 — Details →
v0.2.1 22 Feb 2021 none Apache-2.0 — Details →
v0.2.0 04 Feb 2021 none Apache-2.0 — Details →
v0.1.7-0.20210131230242-4bc354c65c21 31 Jan 2021 none Apache-2.0 — Details →
v0.1.7-0.20210126161304-f6b1ca6c9a58 26 Jan 2021 none Apache-2.0 — Details →
v0.1.6 19 Jan 2021 none Apache-2.0 — Details →
v0.1.5 13 Jan 2021 none Apache-2.0 — Details →
v0.1.4 11 Jan 2021 none Apache-2.0 — Details →
v0.1.3 08 Jan 2021 none Apache-2.0 — Details →
v0.1.2 04 Jan 2021 none Apache-2.0 — Details →
v0.1.1 04 Jan 2021 none Apache-2.0 — Details →
v0.1.0 03 Jan 2021 none Apache-2.0 — Details →
v0.0.0-20210103195449-d48698a44459 03 Jan 2021 none Apache-2.0 — Details →
v0.0.0-20210103124534-38f6feef6b5e 03 Jan 2021 none Apache-2.0 — Details →
v0.0.0-20210103120111-f0017cb44dd3 03 Jan 2021 none Apache-2.0 — Details →
v0.0.0-20201231171727-f13ec19f46cd 31 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201231113040-a7422be2b918 31 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201231094747-323b66c41f90 31 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201230104708-5e1aeb3a380e 30 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201229205024-4f6b3bc8786f 29 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201229203033-1f2361d246b6 29 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201229185254-32411b34192f 29 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201229183711-5b2212afd382 29 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201229182403-2636ce2bbd12 29 Dec 2020 none Apache-2.0 — Details →

All 27 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/di-wu/parser

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/di-wu/parser

Is github.com/di-wu/parser safe to use?

Vulert has no vulnerabilities on record for github.com/di-wu/parser 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/di-wu/parser's Vulert package health score?

Vulert scores github.com/di-wu/parser 44/100, which reads as risky. 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/di-wu/parser affected?

No. v0.3.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 github.com/di-wu/parser should I use?

v0.3.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 github.com/di-wu/parser have?

0 vulnerabilities are recorded for github.com/di-wu/parser 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/di-wu/parser vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/di-wu/parser 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/di-wu/parser 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/di-wu/parser for upcoming vulnerabilities?

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