VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/flosch/pongo2: vulnerability history, versions and safety

github.com/flosch/pongo2 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/flosch/pongo2 vulnerabilities

Vulert verdict on github.com/flosch/pongo2 v0.0.0-20200913210552-0d938eb266f3 i

Updated on 23 Oct 2026

Good news: v0.0.0-20200913210552-0d938eb266f3, the version you would install today, has no known vulnerabilities.

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

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

  • Current release v0.0.0-20200913210552-0d938eb266f3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,081 i
  • OpenSSF scorecard 5/10 i
  • Last release 73 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/flosch/pongo2, 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-20200913210552-0d938eb266f3 13 Sep 2020 none MIT — Details →
v0.0.0-20200913205808-9a66f34c3ce3 13 Sep 2020 none MIT — Details →
v0.0.0-20200805083417-63c99409991d 05 Aug 2020 none MIT — Details →
v0.0.0-20200805082600-a74fe436a15e 05 Aug 2020 none MIT — Details →
v0.0.0-20200529170236-5abacdfa4915 29 May 2020 none MIT — Details →
v0.0.0-20200518135938-dfb43dbdc22a 18 May 2020 none MIT — Details →
v0.0.0-20200518134726-1bd0148030ed 18 May 2020 none MIT — Details →
v0.0.0-20200509134334-76fc00043fe1 09 May 2020 none MIT — Details →
v0.0.0-20190707114632-bbf5a6c351f4 07 Jul 2019 none MIT — Details →
v0.0.0-20190505152737-8914e1cf9164 05 May 2019 none MIT — Details →
v0.0.0-20190505104754-a2b886d1a80a 05 May 2019 none MIT — Details →
v0.0.0-20181225140029-79872a7b2769 25 Dec 2018 none MIT — Details →
v0.0.0-20180809100617-24195e6d38b0 09 Aug 2018 none MIT — Details →
v0.0.0-20180809100235-016b77e7332e 09 Aug 2018 none MIT — Details →
v0.0.0-20180611110828-67f4ff8560df 11 Jun 2018 none MIT — Details →
v0.0.0-20180412215150-e7cf9ea5ca9c 12 Apr 2018 none MIT — Details →
v0.0.0-20180216203047-97eac295f74b 16 Feb 2018 none MIT — Details →
v0.0.0-20170906222041-1f4be1efe3b3 06 Sep 2017 none MIT — Details →
v0.0.0-20170906160657-57613ba146ad 06 Sep 2017 none MIT — Details →
v0.0.0-20170906113737-42418586111b 06 Sep 2017 none MIT — Details →
v0.0.0-20170704123420-58f1f3387f7c 04 Jul 2017 none MIT — Details →
v0.0.0-20170627094943-9d978217a2f8 27 Jun 2017 none MIT — Details →
v0.0.0-20170626232407-813616c5e072 26 Jun 2017 none MIT — Details →
v0.0.0-20170602075643-48b83ca2474f 02 Jun 2017 none MIT — Details →
v0.0.0-20170227155500-1d0f0d3af150 27 Feb 2017 none MIT — Details →
v0.0.0-20170212232125-17d7c034174b 12 Feb 2017 none MIT — Details →
v0.0.0-20170212224023-87c056f95919 12 Feb 2017 none MIT — Details →
v0.0.0-20170124101624-955669f8e9d3 24 Jan 2017 none MIT — Details →
v0.0.0-20160813170523-22499f94d3d5 13 Aug 2016 none MIT — Details →
v0.0.0-20160813150920-031f49e97c46 13 Aug 2016 none MIT — Details →
v0.0.0-20160717141443-5e20832cab69 17 Jul 2016 none MIT — Details →
v0.0.0-20160716051159-0f574306978a 16 Jul 2016 none MIT — Details →
v0.0.0-20160516203445-a026aef7afe7 16 May 2016 none MIT — Details →
v0.0.0-20160316104025-2edc6a896e71 16 Mar 2016 none MIT — Details →
v0.0.0-20160315183058-7f5515449ea9 15 Mar 2016 none MIT — Details →
v0.0.0-20160315141109-18e8cffaf695 15 Mar 2016 none MIT — Details →
v0.0.0-20160219231556-79a0d5e4e032 19 Feb 2016 none MIT — Details →
v0.0.0-20151230152800-c7f4bb7e7890 30 Dec 2015 none MIT — Details →
v0.0.0-20151125110230-f6c21481b698 25 Nov 2015 none MIT — Details →
v0.0.0-20151118000630-a269242022ae 18 Nov 2015 none MIT — Details →
v0.0.0-20151117102544-03283ede4dfe 17 Nov 2015 none MIT — Details →
v0.0.0-20151109163423-e479c70f9eac 09 Nov 2015 none MIT — Details →
v0.0.0-20151105133339-7829d0e14cba 05 Nov 2015 none MIT — Details →
v0.0.0-20151006220256-4bac3860f8ed 06 Oct 2015 none MIT — Details →
v0.0.0-20150929090617-c62e3faa9a5f 29 Sep 2015 none MIT — Details →
v0.0.0-20150821223445-f5d79aa0a914 21 Aug 2015 none MIT — Details →
v0.0.0-20150731100650-0d3f250a1f10 31 Jul 2015 none MIT — Details →
v0.0.0-20150723201012-4b88c21b83c2 23 Jul 2015 none MIT — Details →
v0.0.0-20150723161146-3ebd327c9ecc 23 Jul 2015 none MIT — Details →
v0.0.0-20150703141835-675be51cc980 03 Jul 2015 none MIT — Details →
v0.0.0-20150523110015-5c5c2d876f12 23 May 2015 none MIT — Details →
v0.0.0-20150322125435-c3e5e0ef65b3 22 Mar 2015 none MIT — Details →
v0.0.0-20150309220113-e4c10596e881 09 Mar 2015 none MIT — Details →
v0.0.0-20150214215823-40edabd47a6a 14 Feb 2015 none MIT — Details →
v0.0.0-20141221130753-2ccf0edbd682 21 Dec 2014 none MIT — Details →
v0.0.0-20141218223740-07e273643c22 18 Dec 2014 none MIT — Details →
v0.0.0-20141218223028-f7778727806c 18 Dec 2014 none MIT — Details →
v0.0.0-20141212025717-7a5a378e6eda 12 Dec 2014 none MIT — Details →
v0.0.0-20141206030608-2206c4124448 06 Dec 2014 none MIT — Details →
v0.0.0-20141126165109-0e81af034537 26 Nov 2014 none MIT — Details →
v0.0.0-20141028005603-ca73590a271e 28 Oct 2014 none MIT — Details →
v0.0.0-20141028003105-97072c3325f0 28 Oct 2014 none MIT — Details →
v0.0.0-20141028000813-5e81b817a0c4 28 Oct 2014 none MIT — Details →
v3.0.0-20141028000813-5e81b817a0c4+incompatible 28 Oct 2014 none MIT — Details →
v0.0.0-20141010154010-204751feb995 10 Oct 2014 none MIT — Details →
v0.0.0-20141009021108-bb31c56bd4ba 09 Oct 2014 none MIT — Details →
v0.0.0-20141007130251-238933fedc4c 07 Oct 2014 none MIT — Details →
v0.0.0-20141004161013-1a3b73442e25 04 Oct 2014 none MIT — Details →
v0.0.0-20140919120326-bff5f59f0e25 19 Sep 2014 none MIT — Details →
v0.0.0-20140919103723-b7e499c5b729 19 Sep 2014 none MIT — Details →
v0.0.0-20140918113340-1278c377a0c4 18 Sep 2014 none MIT — Details →
v0.0.0-20140917004338-3000e55d42a8 17 Sep 2014 none MIT — Details →
v0.0.0-20140910102743-3cf40bd547cc 10 Sep 2014 none MIT — Details →
v0.0.0-20140909113316-0ec0d7480672 09 Sep 2014 none MIT — Details →
v0.0.0-20140904151700-dca724a49020 04 Sep 2014 none MIT — Details →
v0.0.0-20140819125321-1a5aec92e885 19 Aug 2014 none MIT — Details →
v0.0.0-20140813022042-68e2374de478 13 Aug 2014 none MIT — Details →
v0.0.0-20140810131521-e534e57a101c 10 Aug 2014 none MIT — Details →
v0.0.0-20140808142729-d0c4746fc187 08 Aug 2014 none MIT — Details →
v0.0.0-20140808141521-05e0111cda86 08 Aug 2014 none MIT — Details →
v0.0.0-20140804220400-ba3523a7390a 04 Aug 2014 none MIT — Details →
v0.0.0-20140804215000-ff8d1f84deb1 04 Aug 2014 none MIT — Details →
v0.0.0-20140801171414-013bfa474354 01 Aug 2014 none MIT — Details →
v0.0.0-20140731142527-078cff641d59 31 Jul 2014 none MIT — Details →
v0.0.0-20140730162727-0773415605a2 30 Jul 2014 none MIT — Details →
v0.0.0-20140729183859-b72ea03dec87 29 Jul 2014 none MIT — Details →
v0.0.0-20140728093259-0dde08b0a1e3 28 Jul 2014 none MIT — Details →
v0.0.0-20140726154107-cd0d5081a54c 26 Jul 2014 none MIT — Details →
v0.0.0-20140722104249-03ecdea6ac75 22 Jul 2014 none MIT — Details →
v0.0.0-20140719155200-2bbbc86aa7d0 19 Jul 2014 none MIT — Details →
v0.0.0-20140718160537-0e401f7c4ffc 18 Jul 2014 none MIT — Details →
v0.0.0-20140718143359-e700c631732a 18 Jul 2014 none MIT — Details →
v0.0.0-20140716222751-07373b86878f 16 Jul 2014 none MIT — Details →
v0.0.0-20140716203240-0637d5d38d01 16 Jul 2014 none MIT — Details →
v0.0.0-20140706143917-192f97cdf2b7 06 Jul 2014 none MIT — Details →
v0.0.0-20140705123918-0328f99bc941 05 Jul 2014 none MIT — Details →
v0.0.0-20140704184304-1e54a393bd76 04 Jul 2014 none MIT — Details →
v0.0.0-20140702211104-0181be45eb59 02 Jul 2014 none MIT — Details →
v0.0.0-20140701192209-0a7a6f7b1722 01 Jul 2014 none MIT — Details →
v0.0.0-20140701190927-60cde10ad72d 01 Jul 2014 none MIT — Details →
v0.0.0-20140629224156-15ea3beee0ab 29 Jun 2014 none — — Details →
v0.0.0-20140628175916-3ec8339a863c 28 Jun 2014 none — — Details →

All 102 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/flosch/pongo2

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/flosch/pongo2

Is github.com/flosch/pongo2 safe to use?

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

Vulert scores github.com/flosch/pongo2 65/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/flosch/pongo2 affected?

No. v0.0.0-20200913210552-0d938eb266f3, 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/flosch/pongo2 should I use?

v0.0.0-20200913210552-0d938eb266f3 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/flosch/pongo2 have?

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

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

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