Vulnerability Database · Go · Package report

github.com/nfnt/resize: vulnerability history, versions and safety

github.com/nfnt/resize 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.

Vulert verdict on github.com/nfnt/resize v0.0.0-20180221191011-83c6a9932646 i

Updated on 23 Oct 2026

Good news: v0.0.0-20180221191011-83c6a9932646, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v0.0.0-20180221191011-83c6a9932646 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,039 i
  • OpenSSF scorecard 1/10 i
  • Last release 104 months ago i
  • Licence ISC 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/nfnt/resize, 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-20180221191011-83c6a9932646 21 Feb 2018 none ISC — Details →
v0.0.0-20180221190546-dd4fa8443fab 21 Feb 2018 none ISC — Details →
v0.0.0-20180221182729-ca1e14ffbddc 21 Feb 2018 none ISC — Details →
v0.0.0-20180221180907-14554cc7daa6 21 Feb 2018 none ISC — Details →
v0.0.0-20161115234754-874f89dba47d 15 Nov 2016 none ISC — Details →
v0.0.0-20160724205520-891127d8d1b5 24 Jul 2016 none ISC — Details →
v0.0.0-20160109112512-4d93a29130b1 09 Jan 2016 none ISC — Details →
v0.0.0-20160107203054-0f9f918da36e 07 Jan 2016 none ISC — Details →
v0.0.0-20160107193421-579058ccc081 07 Jan 2016 none ISC — Details →
v0.0.0-20150527085445-dc93e1b98c57 27 May 2015 none ISC — Details →
v0.0.0-20150525095305-87f723015c05 25 May 2015 none ISC — Details →
v0.0.0-20150512140013-f2d1b73023c5 12 May 2015 none ISC — Details →
v0.0.0-20150512131807-5a6676c19e02 12 May 2015 none ISC — Details →
v0.0.0-20150327185042-ce86eacf2078 27 Mar 2015 none ISC — Details →
v0.0.0-20150327184818-618f7ff07aa1 27 Mar 2015 none ISC — Details →
v0.0.0-20150319195255-0feec0664524 19 Mar 2015 none ISC — Details →
v0.0.0-20150318191943-53e9ca890bcf 18 Mar 2015 none ISC — Details →
v0.0.0-20150315215938-076a9ce3b9fe 15 Mar 2015 none ISC — Details →
v0.0.0-20150315214038-b09281bd3613 15 Mar 2015 none ISC — Details →
v0.0.0-20141217102353-8f4493144849 17 Dec 2014 none ISC — Details →
v0.0.0-20141203184017-87b3f9b01725 03 Dec 2014 none ISC — Details →
v0.0.0-20141121090051-f49722caca08 21 Nov 2014 none ISC — Details →
v0.0.0-20141024124700-7e2ce0a2ea0c 24 Oct 2014 none ISC — Details →
v0.0.0-20141024124149-13ea1287b3e9 24 Oct 2014 none ISC — Details →
v0.0.0-20140915095805-20c6afea041e 15 Sep 2014 none ISC — Details →
v0.0.0-20140915095059-0c6a628df540 15 Sep 2014 none ISC — Details →
v0.0.0-20140820191239-581d15cb5395 20 Aug 2014 none ISC — Details →
v0.0.0-20140820185459-e950449c49f3 20 Aug 2014 none ISC — Details →
v0.0.0-20140813181324-03982f698d03 13 Aug 2014 none ISC — Details →
v0.0.0-20140805160145-ccddecd1bf0b 05 Aug 2014 none ISC — Details →
v0.0.0-20140729223258-427b8d133e71 29 Jul 2014 none ISC — Details →
v0.0.0-20140719111931-016a61cd310d 19 Jul 2014 none ISC — Details →
v0.0.0-20140616035336-f3cac2f86517 16 Jun 2014 none ISC — Details →
v0.0.0-20140130190315-8aee0d995b65 30 Jan 2014 none ISC — Details →
v0.0.0-20140128175457-446eea2f7bf5 28 Jan 2014 none ISC — Details →
v0.0.0-20140118105534-8f586c4f0611 18 Jan 2014 none ISC — Details →
v0.0.0-20140117180530-7c5018c82bea 17 Jan 2014 none ISC — Details →
v0.0.0-20131127214016-b744503c5ce4 27 Nov 2013 none ISC — Details →
v0.0.0-20131118185431-494d8de4e58c 18 Nov 2013 none ISC — Details →
v0.0.0-20130708185546-252ccc84a293 08 Jul 2013 none ISC — Details →
v0.0.0-20130708185520-098f882331f9 08 Jul 2013 none ISC — Details →
v0.0.0-20130704092843-c1b8c4986eed 04 Jul 2013 none ISC — Details →
v0.0.0-20130411183715-33204d8746cd 11 Apr 2013 none ISC — Details →
v0.0.0-20130403184217-09f40122296f 03 Apr 2013 none ISC — Details →
v0.0.0-20130310095808-84039c403bf5 10 Mar 2013 none ISC — Details →
v0.0.0-20130310094606-b6fef854bc97 10 Mar 2013 none ISC — Details →
v0.0.0-20121213211337-82ab8b977c4e 13 Dec 2012 none ISC — Details →
v0.0.0-20121210182721-378e366327fb 10 Dec 2012 none ISC — Details →
v0.0.0-20121210175653-dd1c157427bf 10 Dec 2012 none ISC — Details →
v0.0.0-20121128013819-3d9094eb9e63 28 Nov 2012 none ISC — Details →
v0.0.0-20121114210845-1169a8bfc3dd 14 Nov 2012 none ISC — Details →
v0.0.0-20120904205119-524fd851ea3d 04 Sep 2012 none ISC — Details →
v0.0.0-20120904164904-d93161631c0c 04 Sep 2012 none ISC — Details →
v0.0.0-20120802201615-323dff8a0d28 02 Aug 2012 none — — Details →
v0.0.0-20120802195940-428642c9f1e4 02 Aug 2012 none — — Details →
v0.0.0-20120802194827-9d137a695ece 02 Aug 2012 none — — Details →

All 56 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/nfnt/resize

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/nfnt/resize

Is github.com/nfnt/resize safe to use?

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

Vulert scores github.com/nfnt/resize 58/100, which reads as usable, but worth attention. 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/nfnt/resize affected?

No. v0.0.0-20180221191011-83c6a9932646, 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/nfnt/resize should I use?

v0.0.0-20180221191011-83c6a9932646 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/nfnt/resize have?

0 vulnerabilities are recorded for github.com/nfnt/resize 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/nfnt/resize vulnerabilities disclosed?

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

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