Vulnerability Database · Go · Package report

github.com/filecoin-project/specs-actors/v8: vulnerability history, versions and safety

github.com/filecoin-project/specs-actors/v8 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/filecoin-project/specs-actors/v8 v8.0.1 i

Updated on 23 Oct 2026

Good news: v8.0.1, the version you would install today, has no known vulnerabilities.

Package health score 50/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release v8.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 85 i
  • OpenSSF scorecard 2/10 i
  • Last release 52 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/filecoin-project/specs-actors/v8, 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
v8.0.2-0.20230606144657-985cd0fa0457 06 Jun 2023 none Apache-2.0 — Details →
v8.0.1 10 Jun 2022 none Apache-2.0 — Details →
v8.0.1-0.20220610172802-d8d9867f68a3 10 Jun 2022 none Apache-2.0 — Details →
v8.0.0-20220505175658-9fc35d9a8df0 05 May 2022 none Apache-2.0 — Details →
v8.0.0 22 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220422153930-0afe155bfffa 22 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220414161338-8ff313b3258a 14 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412224951-92abd0e6e7ae 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412191427-ea03df3ebee0 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412190149-ae1ab05bcdb4 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412175552-fe6fa434986b 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412165622-d20705814215 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412135139-3815cb48ef08 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220412064630-4d0ecb61fc9d 12 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220408135446-f61c7056a241 08 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220407213329-8b2d3ecf4294 07 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220407202104-e375a8763a1c 07 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220407194526-5c561a7abed0 07 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220407173458-eb9e09a8182d 07 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220406210313-cc74c2ce729c 06 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220404082322-5f5089f6e8bd 04 Apr 2022 none Apache-2.0 — Details →
v8.0.0-20220325195639-3c87d38a4829 25 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220310174831-d56b240af245 10 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220301040630-7465555c2e22 01 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220301034932-999591726705 01 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220301034615-1c42e1362f54 01 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220301033712-43d1a270b5a1 01 Mar 2022 none Apache-2.0 — Details →
v8.0.0-20220301031434-8a9e0f89e434 01 Mar 2022 none Apache-2.0 — Details →

All 28 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/filecoin-project/specs-actors/v8

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/filecoin-project/specs-actors/v8

Is github.com/filecoin-project/specs-actors/v8 safe to use?

Vulert has no vulnerabilities on record for github.com/filecoin-project/specs-actors/v8 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/filecoin-project/specs-actors/v8's Vulert package health score?

Vulert scores github.com/filecoin-project/specs-actors/v8 50/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/filecoin-project/specs-actors/v8 affected?

No. v8.0.1, 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/filecoin-project/specs-actors/v8 should I use?

v8.0.1 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/filecoin-project/specs-actors/v8 have?

0 vulnerabilities are recorded for github.com/filecoin-project/specs-actors/v8 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/filecoin-project/specs-actors/v8 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/filecoin-project/specs-actors/v8 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/filecoin-project/specs-actors/v8 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/filecoin-project/specs-actors/v8 for upcoming vulnerabilities?

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