Vulnerability Database · npm · Package report
@polkadot-api/json-rpc-provider: vulnerability history, versions and safety
@polkadot-api/json-rpc-provider is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @polkadot-api/json-rpc-provider 0.2.0 i
Updated on 23 Oct 2026
Good news: 0.2.0, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
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
- Depended on by 108 packages i
- Stars 157 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 @polkadot-api/json-rpc-provider, 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.
- 0.2.1-canary.81eb01d 22 Oct 2026
- 0.2.1-canary.0c00cee 22 Oct 2026
- 0.2.1-canary.5ed90b6 22 Oct 2026
- 0.2.1-canary.e652ae2 21 Oct 2026
- 0.2.1-canary.53058b9 20 Oct 2026
- 0.2.1-canary.1af0b85 20 Oct 2026
- 0.2.1-canary.f9b2c7b 16 Oct 2026
- 0.2.1-canary.e8d2b02 15 Oct 2026
- 0.2.1-canary.e14ec93 02 Oct 2026
- 0.2.1-canary.dfa22cf 02 Oct 2026
- 0.2.1-canary.16ff1c2 28 Sep 2026
- 0.2.1-canary.fedd455 28 Sep 2026
- 0.2.1-canary.7a73964 25 Sep 2026
- 0.2.1-canary.9fe0b2a 15 Sep 2026
- 0.2.1-canary.49bdaa9 01 Sep 2026
- 0.2.1-canary.786fa29 01 Sep 2026
- 0.2.1-canary.2bce46a 20 Aug 2026
- 0.2.1-canary.e24aebd 20 Aug 2026
- 0.2.1-canary.d8b2d3d 18 Aug 2026
- 0.2.1-canary.8c00f44 17 Aug 2026
- 0.2.1-canary.57eb571 29 Jul 2026
- 0.2.1-canary.996069a 29 Jul 2026
- 0.2.1-canary.7f105ae 28 Jul 2026
- 0.2.1-canary.9390531 20 Jul 2026
- 0.2.1-canary.22b1f2b 20 Jul 2026
- 0.2.1-canary.0c16fa9 14 Jul 2026
- 0.2.1-canary.45794fa 14 Jul 2026
- 0.2.1-canary.fdb7fff 13 Jul 2026
- 0.2.1-canary.d2a06c4 10 Jul 2026
- 0.2.1-canary.cd20ed6 09 Jul 2026
- 0.2.1-canary.f46ced1 08 Jul 2026
- 0.2.1-canary.7b562b5 07 Jul 2026
- 0.2.1-canary.e751d4b 01 Jul 2026
- 0.2.1-canary.4458833 17 Jun 2026
- 0.2.1-canary.87b9984 12 Jun 2026
- 0.2.1-canary.78aac72 11 Jun 2026
- 0.2.1-canary.845903f 10 Jun 2026
- 0.2.1-canary.813527c 10 Jun 2026
- 0.2.1-canary.ca9c4a7 10 Jun 2026
- 0.2.1-canary.83fad55 03 Jun 2026
- 0.2.1-canary.b804e21 02 Jun 2026
- 0.2.1-canary.20a9091 02 Jun 2026
- 0.2.1-canary.76a35f3 21 May 2026
- 0.2.1-canary.6c794fe 21 May 2026
- 0.2.1-canary.fa9c6bf 21 May 2026
- 0.2.1-canary.b51f624 21 May 2026
- 0.2.1-canary.9d4ef15 19 May 2026
- 0.2.1-canary.5533fce 19 May 2026
- 0.2.1-canary.5ff3ec1 12 May 2026
- 0.2.1-canary.7345de4 12 May 2026
- 0.2.1-canary.f0c9092 12 May 2026
- 0.2.1-canary.8abd5f9 05 May 2026
- 0.2.1-canary.8b0b748 05 May 2026
- 0.2.1-canary.fb86767 04 May 2026
- 0.2.1-canary.9d0f859 04 May 2026
- 0.2.1-canary.636bbb0 04 May 2026
- 0.2.1-canary.92e03a2 30 Apr 2026
- 0.2.1-canary.98f89ed 29 Apr 2026
- 0.2.1-canary.2597fd1 29 Apr 2026
- 0.2.1-canary.ff87070 27 Apr 2026
- 0.2.1-canary.d3dfe9a 27 Apr 2026
- 0.2.1-canary.a3474f0 27 Apr 2026
- 0.2.1-canary.e42e38f 24 Apr 2026
- 0.2.1-canary.8e4c5bb 21 Apr 2026
- 0.2.1-canary.8d48d78 21 Apr 2026
- 0.2.1-canary.9e0a436 20 Apr 2026
- 0.2.1-canary.dabd58e 16 Apr 2026
- 0.2.1-canary.fa37019 15 Apr 2026
- 0.2.1-canary.552fbc3 14 Apr 2026
- 0.2.1-canary.32abdef 13 Apr 2026
- 0.2.1-canary.63b8d92 13 Apr 2026
- 0.2.1-canary.e30969c 10 Apr 2026
- 0.2.1-canary.8387d7c 09 Apr 2026
- 0.2.1-canary.c9e621f 09 Apr 2026
- 0.2.0 08 Apr 2026
- 0.2.1-canary.ccfb151 07 Apr 2026
- 0.1.1-canary.d38c3ed 03 Apr 2026
- 0.1.1-canary.5629cfc 02 Apr 2026
- 0.1.1-canary.2263dae 31 Mar 2026
- 0.1.1-canary.8b5161e 30 Mar 2026
- 0.1.1-canary.d6be873 25 Mar 2026
- 0.1.1-canary.6d36683 24 Mar 2026
- 0.1.1-canary.7bdaf18 18 Mar 2026
- 0.1.1-canary.d1c785a 13 Mar 2026
- 0.1.1-canary.ee039a8 13 Mar 2026
- 0.1.1-canary.f1c6573 13 Mar 2026
- 0.1.1-canary.499775f 12 Mar 2026
- 0.1.1-canary.2975c94 11 Mar 2026
- 0.1.1-canary.cf1413e 09 Mar 2026
- 0.1.1-canary.0faef3b 04 Mar 2026
- 0.1.1-canary.aeb5fb9 04 Mar 2026
- 0.1.1-canary.de92d62 04 Mar 2026
- 0.1.1-canary.9140375 27 Feb 2026
- 0.1.1-canary.6903a4b 19 Feb 2026
- 0.1.1-canary.ec749a6 17 Feb 2026
- 0.1.1-canary.527fbf8 17 Feb 2026
- 0.1.1-canary.9729e61 17 Feb 2026
- 0.1.0 16 Feb 2026
- 1.0.0-canary.baa4c8e 12 Feb 2026
- 1.0.0-canary.e6674af 05 Feb 2026
- 1.0.0-canary.6fe7739 05 Feb 2026
- 1.0.0-canary.3e1307f 29 Jan 2026
- 1.0.0-canary.995c3e6 28 Jan 2026
- 1.0.0-canary.f7f4b6e 22 Jan 2026
- 1.0.0-canary.b168cdc 22 Jan 2026
- 1.0.0-canary.c542ecc 22 Jan 2026
- 1.0.0-canary.a04f26c 22 Jan 2026
- 1.0.0-canary.8e78a51 16 Jan 2026
- 1.0.0-canary.c2c6560 15 Jan 2026
- 1.0.0-canary.22b2fd2 17 Dec 2025
- 1.0.0-canary.30deeea 17 Dec 2025
- 1.0.0-canary.b969ea5 17 Dec 2025
- 1.0.0-canary.ba592c2 17 Dec 2025
- 1.0.0-canary.f69e140 16 Dec 2025
- 1.0.0-canary.478bac8 15 Dec 2025
- 1.0.0-canary.d4a6c2d 15 Dec 2025
- 1.0.0-canary.5b9007d 21 Nov 2025
- 1.0.0-canary.5f20070 31 Oct 2025
- 1.0.0-canary.f545a12 31 Oct 2025
- 1.0.0-canary.b6fd03c 29 Oct 2025
The newest 120 of 721 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 @polkadot-api/json-rpc-provider
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
Questions
About @polkadot-api/json-rpc-provider
Is @polkadot-api/json-rpc-provider safe to use?
Vulert has no vulnerabilities on record for @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider's Vulert package health score?
Vulert scores @polkadot-api/json-rpc-provider 82/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 @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider have?
0 vulnerabilities are recorded for @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider vulnerabilities disclosed?
0 vulnerabilities were recorded for @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider 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 @polkadot-api/json-rpc-provider for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @polkadot-api/json-rpc-provider version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.