VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/Files-com/files-sdk-go/v3: vulnerability history, versions and safety

github.com/Files-com/files-sdk-go/v3 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/Files-com/files-sdk-go/v3 vulnerabilities

Vulert verdict on github.com/Files-com/files-sdk-go/v3 v3.3.323 i

Updated on 23 Oct 2026

Good news: v3.3.323, the version you would install today, has no known vulnerabilities.

Package health score 67/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v3.3.323 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 23 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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/Files-com/files-sdk-go/v3, 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
v3.3.323 22 Oct 2026 none MIT — Details →
v3.3.322 22 Oct 2026 none MIT — Details →
v3.3.321 22 Oct 2026 none MIT — Details →
v3.3.320 21 Oct 2026 none MIT — Details →
v3.3.319 15 Oct 2026 none MIT — Details →
v3.3.318 15 Oct 2026 none MIT — Details →
v3.3.317 15 Oct 2026 none MIT — Details →
v3.3.316 14 Oct 2026 none MIT — Details →
v3.3.315 14 Oct 2026 none MIT — Details →
v3.3.314 13 Oct 2026 none MIT — Details →
v3.3.313 13 Oct 2026 none MIT — Details →
v3.3.312 13 Oct 2026 none MIT — Details →
v3.3.311 13 Oct 2026 none MIT — Details →
v3.3.310 13 Oct 2026 none MIT — Details →
v3.3.309 12 Oct 2026 none MIT — Details →
v3.3.308 12 Oct 2026 none MIT — Details →
v3.3.307 12 Oct 2026 none MIT — Details →
v3.3.306 12 Oct 2026 none MIT — Details →
v3.3.305 12 Oct 2026 none MIT — Details →
v3.3.304 12 Oct 2026 none MIT — Details →
v3.3.303 12 Oct 2026 none MIT — Details →
v3.3.302 11 Oct 2026 none MIT — Details →
v3.3.301 10 Oct 2026 none MIT — Details →
v3.3.300 09 Oct 2026 none MIT — Details →
v3.3.299 09 Oct 2026 none MIT — Details →
v3.3.298 08 Oct 2026 none MIT — Details →
v3.3.297 08 Oct 2026 none MIT — Details →
v3.3.296 06 Oct 2026 none MIT — Details →
v3.3.295 06 Oct 2026 none MIT — Details →
v3.3.294 05 Oct 2026 none MIT — Details →
v3.3.293 05 Oct 2026 none MIT — Details →
v3.3.292 05 Oct 2026 none MIT — Details →
v3.3.291 05 Oct 2026 none MIT — Details →
v3.3.290 04 Oct 2026 none MIT — Details →
v3.3.289 03 Oct 2026 none MIT — Details →
v3.3.288 03 Oct 2026 none MIT — Details →
v3.3.287 03 Oct 2026 none MIT — Details →
v3.3.286 02 Oct 2026 none MIT — Details →
v3.3.285 01 Oct 2026 none MIT — Details →
v3.3.284 01 Oct 2026 none MIT — Details →
v3.3.283 30 Sep 2026 none MIT — Details →
v3.3.282 30 Sep 2026 none MIT — Details →
v3.3.281 30 Sep 2026 none MIT — Details →
v3.3.280 30 Sep 2026 none MIT — Details →
v3.3.279 30 Sep 2026 none MIT — Details →
v3.3.278 30 Sep 2026 none MIT — Details →
v3.3.277 30 Sep 2026 none MIT — Details →
v3.3.276 29 Sep 2026 none MIT — Details →
v3.3.275 29 Sep 2026 none MIT — Details →
v3.3.274 29 Sep 2026 none MIT — Details →
v3.3.273 29 Sep 2026 none MIT — Details →
v3.3.272 28 Sep 2026 none MIT — Details →
v3.3.271 28 Sep 2026 none MIT — Details →
v3.3.270 28 Sep 2026 none MIT — Details →
v3.3.269 28 Sep 2026 none MIT — Details →
v3.3.268 25 Sep 2026 none MIT — Details →
v3.3.267 24 Sep 2026 none MIT — Details →
v3.3.266 23 Sep 2026 none MIT — Details →
v3.3.265 23 Sep 2026 none MIT — Details →
v3.3.264 23 Sep 2026 none MIT — Details →
v3.3.263 23 Sep 2026 none MIT — Details →
v3.3.262 22 Sep 2026 none MIT — Details →
v3.3.261 22 Sep 2026 none MIT — Details →
v3.3.260 21 Sep 2026 none MIT — Details →
v3.3.259 21 Sep 2026 none MIT — Details →
v3.3.258 21 Sep 2026 none MIT — Details →
v3.3.257 20 Sep 2026 none MIT — Details →
v3.3.256 19 Sep 2026 none MIT — Details →
v3.3.255 19 Sep 2026 none MIT — Details →
v3.3.254 17 Sep 2026 none MIT — Details →
v3.3.253 17 Sep 2026 none MIT — Details →
v3.3.252 17 Sep 2026 none MIT — Details →
v3.3.251 17 Sep 2026 none MIT — Details →
v3.3.250 16 Sep 2026 none MIT — Details →
v3.3.249 16 Sep 2026 none MIT — Details →
v3.3.248 15 Sep 2026 none MIT — Details →
v3.3.247 15 Sep 2026 none MIT — Details →
v3.3.246 15 Sep 2026 none MIT — Details →
v3.3.245 15 Sep 2026 none MIT — Details →
v3.3.244 14 Sep 2026 none MIT — Details →
v3.3.243 11 Sep 2026 none MIT — Details →
v3.3.242 10 Sep 2026 none MIT — Details →
v3.3.241 08 Sep 2026 none MIT — Details →
v3.3.240 31 Aug 2026 none MIT — Details →
v3.3.239 31 Aug 2026 none MIT — Details →
v3.3.238 30 Aug 2026 none MIT — Details →
v3.3.237 27 Aug 2026 none MIT — Details →
v3.3.236 27 Aug 2026 none MIT — Details →
v3.3.235 24 Aug 2026 none MIT — Details →
v3.3.234 21 Aug 2026 none MIT — Details →
v3.3.233 17 Aug 2026 none MIT — Details →
v3.3.232 15 Aug 2026 none MIT — Details →
v3.3.231 14 Aug 2026 none MIT — Details →
v3.3.230 13 Aug 2026 none MIT — Details →
v3.3.229 12 Aug 2026 none MIT — Details →
v3.3.228 11 Aug 2026 none MIT — Details →
v3.3.227 11 Aug 2026 none MIT — Details →
v3.3.226 10 Aug 2026 none MIT — Details →
v3.3.225 07 Aug 2026 none MIT — Details →
v3.3.224 07 Aug 2026 none MIT — Details →
v3.3.223 06 Aug 2026 none — — Details →
v3.3.222 06 Aug 2026 none — — Details →
v3.3.221 06 Aug 2026 none — — Details →
v3.3.220 06 Aug 2026 none — — Details →
v3.3.219 05 Aug 2026 none — — Details →
v3.3.218 04 Aug 2026 none — — Details →
v3.3.217 04 Aug 2026 none — — Details →
v3.3.216 04 Aug 2026 none — — Details →
v3.3.215 04 Aug 2026 none — — Details →
v3.3.214 30 Jul 2026 none — — Details →
v3.3.213 29 Jul 2026 none — — Details →
v3.3.212 29 Jul 2026 none — — Details →
v3.3.211 29 Jul 2026 none — — Details →
v3.3.210 28 Jul 2026 none — — Details →
v3.3.209 28 Jul 2026 none — — Details →
v3.3.208 26 Jul 2026 none — — Details →
v3.3.207 25 Jul 2026 none — — Details →
v3.3.206 25 Jul 2026 none — — Details →
v3.3.205 24 Jul 2026 none — — Details →
v3.3.204 22 Jul 2026 none — — Details →

The newest 120 of 818 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/Files-com/files-sdk-go/v3

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/Files-com/files-sdk-go/v3

Is github.com/Files-com/files-sdk-go/v3 safe to use?

Vulert has no vulnerabilities on record for github.com/Files-com/files-sdk-go/v3 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/Files-com/files-sdk-go/v3's Vulert package health score?

Vulert scores github.com/Files-com/files-sdk-go/v3 67/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/Files-com/files-sdk-go/v3 affected?

No. v3.3.323, 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.

How many vulnerabilities does github.com/Files-com/files-sdk-go/v3 have?

0 vulnerabilities are recorded for github.com/Files-com/files-sdk-go/v3 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/Files-com/files-sdk-go/v3 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/Files-com/files-sdk-go/v3 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/Files-com/files-sdk-go/v3 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/Files-com/files-sdk-go/v3 for upcoming vulnerabilities?

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