VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/vincent-petithory/dataurl: vulnerability history, versions and safety

github.com/vincent-petithory/dataurl 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/vincent-petithory/dataurl vulnerabilities

Vulert verdict on github.com/vincent-petithory/dataurl v1.0.0 i

Updated on 23 Oct 2026

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

Package health score 47/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 143 i
  • OpenSSF scorecard 1/10 i
  • Last release 83 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/vincent-petithory/dataurl, 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-20191104211930-d1553a71de50 04 Nov 2019 none MIT — Details →
v1.0.0 04 Nov 2019 none MIT — Details →
v0.0.0-20191104211641-53269b53d97e 04 Nov 2019 none MIT — Details →
v0.0.0-20160330182126-9a301d65acbb 30 Mar 2016 none MIT — Details →
v0.0.0-20160329224706-cee9e7b79e1d 29 Mar 2016 none MIT — Details →
v0.0.0-20141125002513-a81abcdac6cb 25 Nov 2014 none MIT — Details →
v0.0.0-20141125002149-7e45047779f6 25 Nov 2014 none MIT — Details →
v0.0.0-20141124204402-44e525d6213f 24 Nov 2014 none MIT — Details →
v0.0.0-20141026140658-3c3e5e952773 26 Oct 2014 none MIT — Details →
v0.0.0-20141003000645-3a9e6a161d31 03 Oct 2014 none MIT — Details →
v0.0.0-20140610174317-2f8091b4c45c 10 Jun 2014 none MIT — Details →
v0.0.0-20140324205833-1887572e7db2 24 Mar 2014 none MIT — Details →
v0.0.0-20140126155451-1707cd68c309 26 Jan 2014 none MIT — Details →
v0.0.0-20140117132337-0e18ce00cbd2 17 Jan 2014 none — — Details →

All 14 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/vincent-petithory/dataurl

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/vincent-petithory/dataurl

Is github.com/vincent-petithory/dataurl safe to use?

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

Vulert scores github.com/vincent-petithory/dataurl 47/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/vincent-petithory/dataurl affected?

No. v1.0.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/vincent-petithory/dataurl should I use?

v1.0.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/vincent-petithory/dataurl have?

0 vulnerabilities are recorded for github.com/vincent-petithory/dataurl 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/vincent-petithory/dataurl vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/vincent-petithory/dataurl 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/vincent-petithory/dataurl 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/vincent-petithory/dataurl for upcoming vulnerabilities?

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