Vulnerability Database · Go · Package report

github.com/farsightsec/golang-framestream: vulnerability history, versions and safety

github.com/farsightsec/golang-framestream 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/farsightsec/golang-framestream 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 42/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 16 i
  • OpenSSF scorecard 1/10 i
  • Last release 73 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/farsightsec/golang-framestream, 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-20201201145920-f4d0cb589c39 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-271e2319a9db 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-63922cb61ed2 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-85728fbc9490 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-9ea833dae3e7 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-b6862efda285 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-c91275e9b0eb 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201201145920-f4d0cb589c39 01 Dec 2020 none Apache-2.0 — Details →
v0.2.1-0.20201112182833-418f111c613f 12 Nov 2020 none Apache-2.0 — Details →
v0.2.1-0.20200908202652-a227ca6b5004 08 Sep 2020 none Apache-2.0 — Details →
v0.3.0 08 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20190425193708-28af2e89daae 25 Apr 2019 none Apache-2.0 — Details →
v0.0.0-20190425193708-fa4b164d59b8 25 Apr 2019 none Apache-2.0 — Details →
v0.2.0 25 Apr 2019 none Apache-2.0 — Details →
v0.0.0-20181102145529-65a973260480 02 Nov 2018 none Apache-2.0 — Details →
v0.0.0-20181102145529-8a0cb8ba8710 02 Nov 2018 none Apache-2.0 — Details →
v0.0.0-20181102030256-3da2f61c2aeb 02 Nov 2018 none Apache-2.0 — Details →
v0.0.0-20180820161818-d0f7ed81b7af 20 Aug 2018 none Apache-2.0 — Details →
v0.0.0-20180820153532-3caa15725f3f 20 Aug 2018 none Apache-2.0 — Details →
v0.0.0-20180124174429-c06a5734334d 24 Jan 2018 none Apache-2.0 — Details →
v0.0.0-20170911185906-2f4b5e88f090 11 Sep 2017 none Apache-2.0 — Details →
v0.0.0-20170620142824-02269860e8bf 20 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170620142824-dec85654e8b8 20 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170221023045-9ecd69817254 21 Feb 2017 none Apache-2.0 — Details →
v0.0.0-20170130191254-6978081a91b3 30 Jan 2017 none Apache-2.0 — Details →
v0.0.0-20160422005206-b600ccf60674 22 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160408012709-153bb5d9a982 08 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20140211222614-f1c3d3513ad0 11 Feb 2014 none Apache-2.0 — Details →
v0.0.0-20140211222211-0d3d2b530083 11 Feb 2014 none Apache-2.0 — Details →

All 29 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/farsightsec/golang-framestream

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/farsightsec/golang-framestream

Is github.com/farsightsec/golang-framestream safe to use?

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

Vulert scores github.com/farsightsec/golang-framestream 42/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/farsightsec/golang-framestream 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/farsightsec/golang-framestream 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/farsightsec/golang-framestream have?

0 vulnerabilities are recorded for github.com/farsightsec/golang-framestream 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/farsightsec/golang-framestream vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/farsightsec/golang-framestream 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/farsightsec/golang-framestream 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/farsightsec/golang-framestream for upcoming vulnerabilities?

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