Vulnerability Database · npm · Package report

jsox: vulnerability history, versions and safety

Q: How do I monitor jsox for upcoming vulnerabilities?

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

jsox 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 jsox vulnerabilities

Vulert verdict on jsox 1.2.128 i

Updated on 23 Oct 2026

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

Package health score 71/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Inactive

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

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

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for jsox, 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
1.2.128	03 Sep 2026	none	MIT	—	Details →
1.2.126	21 Aug 2026	none	MIT	—	Details →
1.2.125	18 Dec 2025	none	MIT	—	Details →
1.2.124	22 Nov 2025	none	MIT	—	Details →
1.2.123	12 Apr 2025	none	MIT	—	Details →
1.2.122	11 Apr 2025	none	MIT	—	Details →
1.2.121	15 Oct 2024	none	MIT	—	Details →
1.2.120	15 Oct 2024	none	MIT	—	Details →
1.2.119	17 Dec 2023	none	MIT	—	Details →
1.2.118	17 Feb 2023	none	MIT	—	Details →
1.2.117	04 Feb 2023	none	MIT	—	Details →
1.2.116	06 Nov 2022	none	MIT	—	Details →
1.2.115	06 Oct 2022	none	MIT	—	Details →
1.2.114	06 Oct 2022	none	MIT	—	Details →
1.2.113	11 Feb 2022	none	MIT	—	Details →
1.2.112	05 Feb 2022	none	MIT	—	Details →
1.2.111	18 Oct 2021	none	MIT	—	Details →
1.2.110	13 Oct 2021	none	MIT	—	Details →
1.2.109	13 Oct 2021	none	MIT	—	Details →
1.2.108	10 Jan 2021	none	MIT	—	Details →
1.2.107	09 Jan 2021	none	MIT	—	Details →
1.2.106	29 Dec 2020	none	MIT	—	Details →
1.2.105	21 Dec 2020	none	MIT	—	Details →
1.2.104	19 Dec 2020	none	MIT	—	Details →
1.2.103	29 Nov 2020	none	MIT	—	Details →
1.2.102	29 Nov 2020	none	MIT	—	Details →
1.2.101	23 Nov 2020	none	MIT	—	Details →
1.1.121	22 Nov 2019	none	MIT	—	Details →
1.1.120	21 Nov 2019	none	MIT	—	Details →
1.1.118	21 Nov 2019	none	MIT	—	Details →
1.1.117	12 Nov 2019	none	MIT	—	Details →
1.1.116	10 Nov 2019	none	MIT	—	Details →
1.1.115	28 Sep 2019	none	MIT	—	Details →
1.1.114	19 May 2019	none	MIT	—	Details →
1.1.113	04 Apr 2019	none	MIT	—	Details →
1.1.111	26 Mar 2019	none	MIT	—	Details →
1.0.7	07 Oct 2018	none	MIT	—	Details →
1.0.6	22 Sep 2018	none	MIT	—	Details →
1.0.5	22 Sep 2018	none	MIT	—	Details →
1.0.4	17 Sep 2018	none	MIT	—	Details →
1.0.3	17 Sep 2018	none	MIT	—	Details →
1.0.2	17 Sep 2018	none	MIT	—	Details →
1.0.1	14 Sep 2018	none	MIT	—	Details →
1.0.0	12 Sep 2018	none	MIT	—	Details →

All 44 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 jsox

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 jsox

Is jsox safe to use?

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

Vulert scores jsox 71/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 jsox affected?

No. 1.2.128, 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 jsox should I use?

1.2.128 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 jsox have?

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

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

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