VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/samber/oops: vulnerability history, versions and safety

github.com/samber/oops 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/samber/oops vulnerabilities

Vulert verdict on github.com/samber/oops v1.23.2 i

Updated on 23 Oct 2026

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

Package health score 87/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.23.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 995 i
  • Last release 1 month 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/samber/oops, 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-20261001193447-cf12269c1ee4 01 Oct 2026 none MIT — Details →
v1.23.2 14 Sep 2026 none MIT — Details →
v0.0.0-20260914184238-a635f5aaea5d 14 Sep 2026 none MIT — Details →
v0.0.0-20260914184035-5cd89d088222 14 Sep 2026 none MIT — Details →
v0.0.0-20260914183934-5fcade67c01a 14 Sep 2026 none MIT — Details →
v0.0.0-20260901193657-caa656ad11c7 01 Sep 2026 none MIT — Details →
v0.0.0-20260823195244-503ee3b1f345 23 Aug 2026 none MIT — Details →
v1.23.1 23 Aug 2026 none MIT — Details →
v0.0.0-20260801193442-27d16674d0e5 01 Aug 2026 none MIT — Details →
v0.0.0-20260706194052-0c093f0b8805 06 Jul 2026 none MIT — Details →
v1.23.0 06 Jul 2026 none MIT — Details →
v0.0.0-20260705154245-74199a37e433 05 Jul 2026 none MIT — Details →
v0.0.0-20260705151756-53153e5cd381 05 Jul 2026 none MIT — Details →
v0.0.0-20260704173248-470a3a22474d 04 Jul 2026 none MIT — Details →
v0.0.0-20260701193358-844452b37cb7 01 Jul 2026 none MIT — Details →
v0.0.0-20260603134252-c57d8644bc0d 03 Jun 2026 none MIT — Details →
v0.0.0-20260528145910-37b62d050ba2 28 May 2026 none MIT — Details →
v0.0.0-20260528142754-b7740edd661d 28 May 2026 none MIT — Details →
v0.0.0-20260528140835-da4f2469813f 28 May 2026 none MIT — Details →
v0.0.0-20260528133325-5c4605bad7b6 28 May 2026 none MIT — Details →
v1.22.0 26 May 2026 none MIT — Details →
v0.0.0-20260526231738-50ff369e9af7 26 May 2026 none MIT — Details →
v0.0.0-20260524021446-9c5c4af9b2d2 24 May 2026 none MIT — Details →
v0.0.0-20260515165055-5d0edf21ce3a 15 May 2026 none MIT — Details →
v0.0.0-20260504184729-457cdc1d7809 04 May 2026 none MIT — Details →
v0.0.0-20260412154111-1460827f264f 12 Apr 2026 none MIT — Details →
v0.0.0-20260409201923-0372e7b9d26f 09 Apr 2026 none MIT — Details →
v0.0.0-20260409195203-3b4e15c114a9 09 Apr 2026 none MIT — Details →
v0.0.0-20260409175844-0826ddb2d11e 09 Apr 2026 none MIT — Details →
v0.0.0-20260407233437-b85b04a841c2 07 Apr 2026 none MIT — Details →
v0.0.0-20260407231844-828fba435932 07 Apr 2026 none MIT — Details →
v0.0.0-20260406183847-bc13c7a828dc 06 Apr 2026 none MIT — Details →
v0.0.0-20260406154246-13cd300e3bcf 06 Apr 2026 none MIT — Details →
v0.0.0-20260406133710-5748a6c9ba2b 06 Apr 2026 none MIT — Details →
v0.0.0-20260406133054-5beb0e822ad6 06 Apr 2026 none MIT — Details →
v0.0.0-20260406125104-69cddd712d0a 06 Apr 2026 none MIT — Details →
v0.0.0-20260406120750-3100ff34c968 06 Apr 2026 none MIT — Details →
v0.0.0-20260402170550-f43e94be84d4 02 Apr 2026 none MIT — Details →
v0.0.0-20260402010450-6bc5b2c00d92 02 Apr 2026 none MIT — Details →
v0.0.0-20260325233024-fdc4d78178db 25 Mar 2026 none MIT — Details →
v0.0.0-20260323031308-0102cc933be9 23 Mar 2026 none MIT — Details →
v0.0.0-20260225193831-1a99714a330e 25 Feb 2026 none MIT — Details →
v1.21.0 18 Jan 2026 none MIT — Details →
v0.0.0-20260118214853-5a99d5f9cee9 18 Jan 2026 none MIT — Details →
v0.0.0-20260115113324-2abf8f20931c 15 Jan 2026 none MIT — Details →
v0.0.0-20260115014733-028e5cfecec3 15 Jan 2026 none MIT — Details →
v1.20.0 01 Jan 2026 none MIT — Details →
v0.0.0-20260101195714-ee59589fe6d3 01 Jan 2026 none MIT — Details →
v0.0.0-20251205112451-56a34a134482 05 Dec 2025 none MIT — Details →
v0.0.0-20251202023831-59c0e072736b 02 Dec 2025 none MIT — Details →
v1.19.4 13 Nov 2025 none MIT — Details →
v0.0.0-20251113202025-2ee3b2cd9d82 13 Nov 2025 none MIT — Details →
v0.0.0-20251113201742-1f89af38bc79 13 Nov 2025 none MIT — Details →
v0.0.0-20251107145304-5481e506bcfa 07 Nov 2025 none MIT — Details →
v0.0.0-20251101194211-1af48784ca1f 01 Nov 2025 none MIT — Details →
v0.0.0-20251001191327-af22ba323515 01 Oct 2025 none MIT — Details →
v1.19.3 01 Oct 2025 none MIT — Details →
v0.19.2 01 Oct 2025 none MIT — Details →
v0.0.0-20251001140341-010e151d590e 01 Oct 2025 none MIT — Details →
v0.0.0-20251001140116-033a8392b261 01 Oct 2025 none MIT — Details →
v0.0.0-20250926170948-368ea46546a7 26 Sep 2025 none MIT — Details →
v0.0.0-20250925135417-03af5420e6f0 25 Sep 2025 none MIT — Details →
v0.0.0-20250902142136-058d517ffd2b 02 Sep 2025 none MIT — Details →
v0.0.0-20250902140824-6722ce22f0ac 02 Sep 2025 none MIT — Details →
v0.0.0-20250826180631-20d910524fc6 26 Aug 2025 none MIT — Details →
v0.0.0-20250812145139-8b7d78ba0d89 12 Aug 2025 none MIT — Details →
v0.0.0-20250729144312-125fbb0d7bc6 29 Jul 2025 none MIT — Details →
v0.0.0-20250729140238-84574337814a 29 Jul 2025 none MIT — Details →
v0.0.0-20250729120752-c249f9e37246 29 Jul 2025 none MIT — Details →
v0.0.0-20250706145642-cd991be35e42 06 Jul 2025 none MIT — Details →
v0.0.0-20250706144736-d3889de7543f 06 Jul 2025 none MIT — Details →
v0.0.0-20250705125727-d0c9730907cb 05 Jul 2025 none MIT — Details →
v0.19.1 30 Jun 2025 none MIT — Details →
v0.0.0-20250630170056-ef7b9760d2de 30 Jun 2025 none MIT — Details →
v0.0.0-20250630160307-b4c2ed5a5b1f 30 Jun 2025 none MIT — Details →
v0.0.0-20250629133542-4e171a4a25e9 29 Jun 2025 none MIT — Details →
v1.19.0 27 Jun 2025 none MIT — Details →
v0.0.0-20250627142605-b982776c3cae 27 Jun 2025 none MIT — Details →
v0.0.0-20250627141917-d399f7f92ec4 27 Jun 2025 none MIT — Details →
v0.0.0-20250627135644-2f2b1f5fc314 27 Jun 2025 none MIT — Details →
v0.0.0-20250627134731-8e8b0d0feb89 27 Jun 2025 none MIT — Details →
v0.0.0-20250627134103-038b734d07b2 27 Jun 2025 none MIT — Details →
v0.0.0-20250625165502-efee22c6fc17 25 Jun 2025 none MIT — Details →
v0.0.0-20250617094048-2f6414b971ec 17 Jun 2025 none MIT — Details →
v1.18.1 27 May 2025 none MIT — Details →
v0.0.0-20250527213707-75067ba09442 27 May 2025 none MIT — Details →
v0.0.0-20250526223731-4218dc5df851 26 May 2025 none MIT — Details →
v1.18.0 21 May 2025 none MIT — Details →
v0.0.0-20250521144759-1bdea12a28fb 21 May 2025 none MIT — Details →
v0.0.0-20250505202012-367f25c0fe94 05 May 2025 none MIT — Details →
v0.0.0-20250429154547-306f1fe1e72e 29 Apr 2025 none MIT — Details →
v0.0.0-20250427171417-d155b2535137 27 Apr 2025 none MIT — Details →
v0.0.0-20250423230942-63858a4de8f8 23 Apr 2025 none MIT — Details →
v0.0.0-20250325105801-8ad4ec6f86f5 25 Mar 2025 none MIT — Details →
v1.17.0 05 Mar 2025 none MIT — Details →
v0.0.0-20250305134019-3f82677d653d 05 Mar 2025 none MIT — Details →
v0.0.0-20250304193809-eeb65a7c1b00 04 Mar 2025 none MIT — Details →
v1.16.1 23 Feb 2025 none MIT — Details →
v0.0.0-20250223150152-e3d0bb6495c4 23 Feb 2025 none MIT — Details →
v0.0.0-20250203203049-54078d1c81c2 03 Feb 2025 none MIT — Details →
v1.16.0 03 Feb 2025 none — — Details →
v0.0.0-20250203173701-85e23be0bb0e 03 Feb 2025 none — — Details →
v0.0.0-20250127200623-a04cb8baf383 27 Jan 2025 none — — Details →
v0.0.0-20250125011319-f80ce4f9293b 25 Jan 2025 none — — Details →
v0.0.0-20250122095100-d8fe16b279dc 22 Jan 2025 none — — Details →
v0.0.0-20250118171750-5f260aa70a0f 18 Jan 2025 none — — Details →
v1.15.0 19 Dec 2024 none — — Details →
v0.0.0-20241219000142-30e9393f394a 19 Dec 2024 none — — Details →
v0.0.0-20241207163631-1fb0d3425d72 07 Dec 2024 none — — Details →
v1.14.2 06 Dec 2024 none — — Details →
v0.0.0-20241206094913-d4a45b1b4225 06 Dec 2024 none — — Details →
v0.0.0-20241125214145-5e8573e1a89d 25 Nov 2024 none — — Details →
v0.0.0-20241119090920-bcc5b2abd283 19 Nov 2024 none — — Details →
v0.0.0-20241110221422-c3339dc3828c 10 Nov 2024 none — — Details →
v1.14.1 05 Nov 2024 none — — Details →
v0.0.0-20241105011706-0af95f6eb4a5 05 Nov 2024 none — — Details →
v1.14.0 05 Nov 2024 none — — Details →
v0.0.0-20241104235909-ad72a71e274a 04 Nov 2024 none — — Details →
v1.13.1 20 Aug 2024 none — — Details →
v0.0.0-20240820203127-cd49394e977e 20 Aug 2024 none — — Details →

The newest 120 of 183 versions Vulert tracks. 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/samber/oops

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/samber/oops

Is github.com/samber/oops safe to use?

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

Vulert scores github.com/samber/oops 87/100, which reads as healthy. 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/samber/oops affected?

No. v1.23.2, 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/samber/oops should I use?

v1.23.2 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/samber/oops have?

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

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

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