VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@farcaster/frame-sdk: vulnerability history, versions and safety

@farcaster/frame-sdk is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm 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 @farcaster/frame-sdk vulnerabilities

Vulert verdict on @farcaster/frame-sdk 0.2.0 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 0.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 6 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 @farcaster/frame-sdk, 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
0.0.0-canary-20260804185713 04 Aug 2026 none MIT — Details →
0.0.0-canary-20260804184919 04 Aug 2026 none MIT — Details →
0.2.0 01 Apr 2026 none MIT — Details →
0.0.0-canary-20260331220304 31 Mar 2026 none MIT — Details →
0.1.14 05 Feb 2026 none MIT — Details →
0.0.0-canary-20260205001141 05 Feb 2026 none MIT — Details →
0.0.0-canary-20260204234855 04 Feb 2026 none MIT — Details →
0.0.0-canary-20260204233206 04 Feb 2026 none MIT — Details →
0.1.13 26 Jan 2026 none MIT — Details →
0.0.0-canary-20260126193718 26 Jan 2026 none MIT — Details →
0.0.0-canary-20260126190937 26 Jan 2026 none MIT — Details →
0.0.0-canary-20260126185232 26 Jan 2026 none MIT — Details →
0.0.0-canary-20260123200319 23 Jan 2026 none MIT — Details →
0.1.12 16 Oct 2025 none MIT — Details →
0.0.0-canary-20251016150758 16 Oct 2025 none MIT — Details →
0.1.11 09 Oct 2025 none MIT — Details →
0.0.0-canary-20250926142931 26 Sep 2025 none MIT — Details →
0.1.10 05 Sep 2025 none MIT — Details →
0.0.0-canary-20250905164304 05 Sep 2025 none MIT — Details →
0.1.9 16 Aug 2025 none MIT — Details →
0.0.0-canary-20250816182708 16 Aug 2025 none MIT — Details →
0.1.8 26 Jul 2025 none MIT — Details →
0.0.0-canary-20250726165352 26 Jul 2025 none MIT — Details →
0.1.7 13 Jul 2025 none MIT — Details →
0.0.0-canary-20250713234517 13 Jul 2025 none MIT — Details →
0.1.6 08 Jul 2025 none MIT — Details →
0.0.0-canary-20250708031428 08 Jul 2025 none MIT — Details →
0.1.5 07 Jul 2025 none MIT — Details →
0.0.0-canary-20250707200948 07 Jul 2025 none MIT — Details →
0.1.4 05 Jul 2025 none MIT — Details →
0.0.0-canary-20250705153407 05 Jul 2025 none MIT — Details →
0.1.3 05 Jul 2025 none MIT — Details →
0.0.0-canary-20250705122814 05 Jul 2025 none MIT — Details →
0.1.2 01 Jul 2025 none MIT — Details →
0.0.0-canary-20250701152931 01 Jul 2025 none MIT — Details →
0.1.1 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630230419 30 Jun 2025 none MIT — Details →
0.1.0 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630212526 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630212339 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630194123 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630153244 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630152811 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250630152209 30 Jun 2025 none MIT — Details →
0.0.0-canary-20250627225801 27 Jun 2025 none MIT — Details →
0.0.0-canary-20250627221609 27 Jun 2025 none MIT — Details →
0.0.0-canary-20250627221200 27 Jun 2025 none MIT — Details →
0.0.0-canary-20250627220701 27 Jun 2025 none MIT — Details →
0.0.0-canary-20250627215855 27 Jun 2025 none MIT — Details →
0.0.0-canary-20250627213014 27 Jun 2025 none MIT — Details →
0.0.64 17 Jun 2025 none MIT — Details →
0.0.0-canary-20250617161540 17 Jun 2025 none MIT — Details →
0.0.63 11 Jun 2025 none MIT — Details →
0.0.0-canary-20250611151843 11 Jun 2025 none MIT — Details →
0.0.0-canary-20250611145932 11 Jun 2025 none MIT — Details →
0.0.0-canary-20250610142916 10 Jun 2025 none MIT — Details →
0.0.61 09 Jun 2025 none MIT — Details →
0.0.0-canary-20250609214530 09 Jun 2025 none MIT — Details →
0.0.60 05 Jun 2025 none MIT — Details →
0.0.0-canary-20250605220746 05 Jun 2025 none MIT — Details →
0.0.59 05 Jun 2025 none MIT — Details →
0.0.0-canary-20250605201932 05 Jun 2025 none MIT — Details →
0.0.58 05 Jun 2025 none MIT — Details →
0.0.0-canary-20250605194947 05 Jun 2025 none MIT — Details →
0.0.57 04 Jun 2025 none MIT — Details →
0.0.0-canary-20250604194009 04 Jun 2025 none MIT — Details →
0.0.56 04 Jun 2025 none MIT — Details →
0.0.0-canary-20250604181208 04 Jun 2025 none MIT — Details →
0.0.0-canary-20250604173458 04 Jun 2025 none MIT — Details →
0.0.0-canary-20250604165959 04 Jun 2025 none MIT — Details →
0.0.55 03 Jun 2025 none MIT — Details →
0.0.0-canary-20250603193719 03 Jun 2025 none MIT — Details →
0.0.54 03 Jun 2025 none MIT — Details →
0.0.0-canary-20250603021841 03 Jun 2025 none MIT — Details →
0.0.53 27 May 2025 none MIT — Details →
0.0.0-canary-20250527172418 27 May 2025 none MIT — Details →
0.0.52 27 May 2025 none MIT — Details →
0.0.0-canary-20250527060117 27 May 2025 none MIT — Details →
0.0.51 23 May 2025 none MIT — Details →
0.0.0-canary-20250523204431 23 May 2025 none MIT — Details →
0.0.50 22 May 2025 none MIT — Details →
0.0.0-canary-20250522044311 22 May 2025 none MIT — Details →
0.0.49 22 May 2025 none MIT — Details →
0.0.0-canary-20250522022704 22 May 2025 none MIT — Details →
0.0.48 20 May 2025 none MIT — Details →
0.0.0-canary-20250520204042 20 May 2025 none MIT — Details →
0.0.47 20 May 2025 none MIT — Details →
0.0.0-canary-20250520181919 20 May 2025 none MIT — Details →
0.0.46 20 May 2025 none MIT — Details →
0.0.0-canary-20250520173105 20 May 2025 none MIT — Details →
0.0.45 17 May 2025 none MIT — Details →
0.0.0-canary-20250517141806 17 May 2025 none MIT — Details →
0.0.44 16 May 2025 none MIT — Details →
0.0.0-canary-20250516165341 16 May 2025 none MIT — Details →
0.0.0-canary-20250516165206 16 May 2025 none MIT — Details →
0.0.43 16 May 2025 none MIT — Details →
0.0.0-canary-20250516033422 16 May 2025 none MIT — Details →
0.0.0-canary-20250516031050 16 May 2025 none MIT — Details →
0.0.0-canary-20250515203543 15 May 2025 none MIT — Details →
0.0.0-canary-20250515200421 15 May 2025 none MIT — Details →
0.0.41 13 May 2025 none — — Details →
0.0.0-canary-20250513184040 13 May 2025 none — — Details →
0.0.0-canary-20250513182339 13 May 2025 none — — Details →
0.0.40 13 May 2025 none — — Details →
0.0.0-canary-20250513054347 13 May 2025 none — — Details →
0.0.0-canary-20250513052234 13 May 2025 none — — Details →
0.0.0-canary-20250513031424 13 May 2025 none — — Details →
0.0.0-canary-20250512195326 12 May 2025 none — — Details →
0.0.0-canary-20250512195041 12 May 2025 none — — Details →
0.0.0-canary-20250512194707 12 May 2025 none — — Details →
0.0.0-canary-20250512185912 12 May 2025 none — — Details →
0.0.39 11 May 2025 none — — Details →
0.0.0-canary-20250511031627 11 May 2025 none — — Details →
0.0.0-canary-20250510210542 10 May 2025 none — — Details →
0.0.0-canary-20250510204457 10 May 2025 none — — Details →
0.0.0-canary-20250509172815 09 May 2025 none — — Details →
0.0.0-canary-20250509164556 09 May 2025 none — — Details →
0.0.0-canary-20250508234838 08 May 2025 none — — Details →
0.0.0-canary-20250508220359 08 May 2025 none — — Details →
0.0.0-canary-20250508220243 08 May 2025 none — — Details →

The newest 120 of 161 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 @farcaster/frame-sdk

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 @farcaster/frame-sdk

Is @farcaster/frame-sdk safe to use?

Vulert has no vulnerabilities on record for @farcaster/frame-sdk in npm 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 @farcaster/frame-sdk's Vulert package health score?

Vulert scores @farcaster/frame-sdk 76/100, which reads as in good shape. 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 @farcaster/frame-sdk affected?

No. 0.2.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 @farcaster/frame-sdk should I use?

0.2.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 @farcaster/frame-sdk have?

0 vulnerabilities are recorded for @farcaster/frame-sdk in the npm 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 @farcaster/frame-sdk vulnerabilities disclosed?

0 vulnerabilities were recorded for @farcaster/frame-sdk 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 @farcaster/frame-sdk 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 @farcaster/frame-sdk for upcoming vulnerabilities?

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