Vulnerability Database · npm · Package report

deasync: vulnerability history, versions and safety

Q: How do I monitor deasync for upcoming vulnerabilities?

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

deasync is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all deasync vulnerabilities

Vulert verdict on deasync 0.1.32 i

Updated on 23 Oct 2026

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

Package health score 79/100

Security Minor issues
Maintenance Sustainable
Popularity Widely used
Community Quiet

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

Current release 0.1.32 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 3,812 packages i
Stars 1,005 i
OpenSSF scorecard 2/10 i
Last release this month 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for deasync, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.1.32	12 Oct 2026	none	MIT	—	Details →
0.1.31	13 Nov 2025	none	MIT	—	Details →
0.1.30	02 Jun 2024	none	MIT	—	Details →
0.1.29	21 Oct 2023	none	MIT	—	Details →
0.1.28	07 Aug 2022	none	MIT	—	Details →
0.1.27	06 Jul 2022	none	MIT	—	Details →
0.1.26	01 Apr 2022	none	MIT	—	Details →
0.1.25	30 Mar 2022	none	MIT	—	Details →
0.1.24	11 Nov 2021	none	MIT	—	Details →
0.1.23	24 Aug 2021	none	MIT	—	Details →
0.1.22	05 Aug 2021	none	MIT	—	Details →
0.1.21	07 Nov 2020	none	MIT	—	Details →
0.1.20	27 Apr 2020	none	MIT	—	Details →
0.1.19	20 Dec 2019	none	MIT	—	Details →
0.1.18	19 Dec 2019	none	MIT	—	Details →
0.1.17	19 Dec 2019	none	MIT	—	Details →
0.1.16	17 Nov 2019	none	MIT	—	Details →
0.1.15	04 May 2019	none	MIT	—	Details →
0.1.14	13 Nov 2018	none	MIT	—	Details →
0.1.13	10 May 2018	none	MIT	—	Details →
0.1.12	14 Dec 2017	none	MIT	—	Details →
0.1.11	17 Nov 2017	none	MIT	—	Details →
0.1.10	06 Jun 2017	none	MIT	—	Details →
0.1.9	29 Oct 2016	none	MIT	—	Details →
0.1.8	01 Oct 2016	none	MIT	—	Details →
0.1.7	28 May 2016	none	MIT	—	Details →
0.1.6	30 Apr 2016	none	MIT	—	Details →
0.1.5	23 Apr 2016	none	MIT	—	Details →
0.1.4	16 Nov 2015	none	MIT	—	Details →
0.1.3	09 Oct 2015	none	MIT	—	Details →
0.1.2	14 Sep 2015	none	MIT	—	Details →
0.1.1	30 Aug 2015	none	MIT	—	Details →
0.1.0	18 May 2015	none	MIT	—	Details →
0.0.10	12 Feb 2015	none	MIT	—	Details →
0.0.9	08 Feb 2015	none	MIT	—	Details →
0.0.8	25 Jan 2015	none	MIT	—	Details →
0.0.7	31 Mar 2014	none	MIT	—	Details →
0.0.6	30 Mar 2014	none	MIT	—	Details →
0.0.5	30 Mar 2014	none	MIT	—	Details →
0.0.4	30 Mar 2014	none	MIT	—	Details →
0.0.3	30 Mar 2014	none	MIT	—	Details →

All 41 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for deasync

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 deasync

Is deasync safe to use?

Vulert has no vulnerabilities on record for deasync 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 deasync's Vulert package health score?

Vulert scores deasync 79/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 deasync affected?

No. 0.1.32, 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 deasync have?

0 vulnerabilities are recorded for deasync 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 deasync vulnerabilities disclosed?

0 vulnerabilities were recorded for deasync 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 deasync 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 deasync for upcoming vulnerabilities?

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