Vulnerability Database · npm · Package report

linqts: vulnerability history, versions and safety

Q: How do I monitor linqts for upcoming vulnerabilities?

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

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

Vulert verdict on linqts 3.4.0 i

Updated on 23 Oct 2026

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

Package health score 75/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Quiet

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

Current release 3.4.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 3 packages i
Stars 881 i
OpenSSF scorecard 3/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 linqts, 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
3.4.0	16 Oct 2026	none	MIT	—	Details →
3.3.0	02 Jul 2026	none	MIT	—	Details →
3.2.0	09 Sep 2025	none	MIT	—	Details →
3.1.0	23 Jul 2025	none	MIT	—	Details →
3.0.0	21 Jul 2025	none	MIT	—	Details →
2.0.0	01 Aug 2024	none	MIT	—	Details →
1.15.0	16 May 2023	none	MIT	—	Details →
1.14.4	12 Jan 2021	none	MIT	—	Details →
1.14.3	19 Aug 2020	none	MIT	—	Details →
1.14.2	05 Jun 2020	none	MIT	—	Details →
1.14.1	05 Jun 2020	none	MIT	—	Details →
1.14.0	01 Jun 2020	none	MIT	—	Details →
1.13.0	08 May 2020	none	MIT	—	Details →
1.12.6	02 Aug 2019	none	MIT	—	Details →
1.12.5	20 Jun 2019	none	MIT	—	Details →
1.12.4	12 Jun 2019	none	MIT	—	Details →
1.12.3	12 Jun 2019	none	MIT	—	Details →
1.12.2	03 Nov 2018	none	MIT	—	Details →
1.12.1	30 Oct 2018	none	MIT	—	Details →
0.0.0-semantic-release	30 Oct 2018	none	MIT	—	Details →
1.12.0	07 Jul 2018	none	MIT	—	Details →
1.11.0	14 Mar 2018	none	MIT	—	Details →
1.10.3	10 Mar 2018	none	MIT	—	Details →
1.10.2	02 Mar 2018	none	MIT	—	Details →
1.10.1	21 Feb 2018	none	MIT	—	Details →
1.10.0	04 Sep 2017	none	MIT	—	Details →
1.9.1	20 Jul 2017	none	MIT	—	Details →
1.9.0	19 Jul 2017	none	MIT	—	Details →
1.8.3	06 Jul 2017	none	MIT	—	Details →
1.8.2	28 Apr 2017	none	MIT	—	Details →
1.8.1	24 Mar 2017	none	MIT	—	Details →
1.8.0	27 Feb 2017	none	MIT	—	Details →
1.7.5	16 Feb 2017	none	MIT	—	Details →
1.7.4	17 Jan 2017	none	MIT	—	Details →
1.7.3	16 Jan 2017	none	MIT	—	Details →
1.7.2	11 Jan 2017	none	MIT	—	Details →
1.7.1	29 Dec 2016	none	MIT	—	Details →
1.7.0	14 Dec 2016	none	MIT	—	Details →
1.6.2	12 Dec 2016	none	MIT	—	Details →
1.6.1	25 Nov 2016	none	MIT	—	Details →
1.6.0	09 Aug 2016	none	MIT	—	Details →
1.5.0	05 Jun 2016	none	MIT	—	Details →
1.4.0	26 May 2016	none	MIT	—	Details →
1.3.1	17 May 2016	none	MIT	—	Details →
1.3.0	04 May 2016	none	MIT	—	Details →
1.2.2	21 Apr 2016	none	MIT	—	Details →
1.2.1	07 Apr 2016	none	MIT	—	Details →
1.2.0	07 Apr 2016	none	MIT	—	Details →
1.1.1	01 Apr 2016	none	MIT	—	Details →
1.0.1	31 Mar 2016	none	MIT	—	Details →
1.0.0	25 Mar 2016	none	MIT	—	Details →
0.9.1	23 Mar 2016	none	MIT	—	Details →
0.9.0	22 Mar 2016	none	MIT	—	Details →
0.7.0	21 Mar 2016	none	MIT	—	Details →
0.6.0	20 Mar 2016	none	MIT	—	Details →
0.5.0	20 Mar 2016	none	MIT	—	Details →
0.4.0	17 Mar 2016	none	MIT	—	Details →
0.3.0	15 Mar 2016	none	MIT	—	Details →
0.2.0	14 Mar 2016	none	MIT	—	Details →
0.1.3	13 Mar 2016	none	MIT	—	Details →
0.1.2	13 Mar 2016	none	MIT	—	Details →
0.1.1	13 Mar 2016	none	MIT	—	Details →
0.1.0	11 Mar 2016	none	MIT	—	Details →

All 63 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 linqts

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 linqts

Is linqts safe to use?

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

Vulert scores linqts 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 linqts affected?

No. 3.4.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.

How many vulnerabilities does linqts have?

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

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

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