Vulnerability Database · npm · Package report

isows: vulnerability history, versions and safety

isows 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.

Vulert verdict on isows 1.0.7 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Inactive

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

  • Current release 1.0.7 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 33,563 packages i
  • Stars 59 i
  • Last release 17 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 isows, 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
1.0.7 13 May 2025 none MIT — Details →
0.0.0-main.20250513T193453 13 May 2025 none MIT — Details →
0.0.0-main.20250513T193128 13 May 2025 none MIT — Details →
0.0.0-main.20250513T190543 13 May 2025 none MIT — Details →
0.0.0-main.20250513T185817 13 May 2025 none MIT — Details →
0.0.0-main.20250513T185537 13 May 2025 none MIT — Details →
0.0.0-main.20250513T184914 13 May 2025 none MIT — Details →
1.0.6 30 Sep 2024 none MIT — Details →
0.0.0-main.20240930T071753 30 Sep 2024 none MIT — Details →
1.0.4 15 Mar 2024 none MIT — Details →
0.0.0-main.20240315T045016 15 Mar 2024 none MIT — Details →
0.0.0-main.20240315T044632 15 Mar 2024 none MIT — Details →
0.0.0-main.20240314T203659 14 Mar 2024 none MIT — Details →
0.0.0-main.20240314T202059 14 Mar 2024 none MIT — Details →
0.0.0-main.20240314T201836 14 Mar 2024 none MIT — Details →
0.0.0-main.20231101T034210 01 Nov 2023 none MIT — Details →
1.0.3 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T213017 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T212500 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T212427 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T212114 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T211001 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T210111 09 Oct 2023 none MIT — Details →
0.0.0-main.20231009T210044 09 Oct 2023 none MIT — Details →
1.0.2 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T195446 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T195156 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T194852 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T194613 08 Oct 2023 none MIT — Details →
1.0.1 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T093342 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T092742 08 Oct 2023 none MIT — Details →
1.0.0 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T072822 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T072313 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T071851 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T071758 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T071746 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T071658 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T070151 08 Oct 2023 none MIT — Details →
0.0.1 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T064905 08 Oct 2023 none MIT — Details →
0.0.0-main.20231008T064629 08 Oct 2023 none MIT — Details →

All 43 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 isows

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 isows

Is isows safe to use?

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

Vulert scores isows 75/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 isows affected?

No. 1.0.7, 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 isows should I use?

1.0.7 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 isows have?

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

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

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