Is nodeschnaps safe to use?

Vulert records 1 vulnerabilities for nodeschnaps in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is nodeschnaps's Vulert package health score?

Vulert scores nodeschnaps 50/100, which reads as usable, but worth attention. 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 nodeschnaps affected?

Yes. 0.12.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of nodeschnaps should I use?

0.12.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 nodeschnaps have?

1 vulnerability is recorded for nodeschnaps in the npm ecosystem: 0 critical, 1 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 nodeschnaps vulnerabilities disclosed?

0 vulnerabilities were recorded for nodeschnaps in the last 12 months, and the oldest entry in this database dates to 18 Feb 2019. 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 nodeschnaps 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 nodeschnaps for upcoming vulnerabilities?

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

Vulnerability Database · npm · Package report

nodeschnaps: vulnerability history, versions and safety

nodeschnaps is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 19 releases, first recorded in Feb 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded H1

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

Vulert verdict on nodeschnaps 0.12.0 i

Updated on 23 Oct 2026

Action needed: 0.12.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 50/100

Security Minor issues
Maintenance Slowing
Popularity Little adoption
Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

Current release 0.12.0 — affected i
Vulnerabilities on record 1 over 1 year · 0 in the last year i
Latest disclosure 18 Feb 2019 i
Highest CVSS n/a i
With no published fix 0 i
Stars 18 i
OpenSSF scorecard 1/10 i
Last release 86 months ago i
Licence LGPL-3.0 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 nodeschnaps, 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.12.0	07 Aug 2019	H1	LGPL-3.0	Yes	Details →
0.11.0	18 Jan 2019	H1	LGPL-3.0	Yes	Details →
0.10.0	08 Mar 2018	H1	LGPL-3.0	Yes	Details →
0.9.1	18 Nov 2017	H1	LGPL-3.0	Yes	Details →
0.9.0	13 Nov 2017	H1	LGPL-3.0	Yes	Details →
0.8.0	18 Oct 2017	H1	LGPL-3.0	Yes	Details →
0.7.0	03 Apr 2017	H1	LGPL-3.0	Yes	Details →
0.6.1	10 Mar 2016	H1	LGPL-3.0	Yes	Details →
0.6.0	18 Feb 2016	H1	LGPL-3.0	Yes	Details →
0.5.3	11 Nov 2015	H1	LGPL-3.0	Yes	Details →
0.5.2	09 Sep 2015	H1	LGPL-3.0	Yes	Details →
0.5.1	13 Jul 2015	H1	LGPL-3.0	Yes	Details →
0.5.0	21 Jun 2015	H1	LGPL-3.0	Yes	Details →
0.4.1	09 Jun 2015	H1	LGPL-3.0	Yes	Details →
0.4.0	03 Feb 2015	H1	LGPL-3.0	Yes	Details →
0.3.1	01 Sep 2014	H1	LGPL-3.0	Yes	Details →
0.3.0	31 Aug 2014	H1	LGPL-3.0	Yes	Details →
0.2.0	17 Aug 2014	H1	LGPL-3.0	Yes	Details →
0.1.0	30 Jul 2014	H1	LGPL-3.0	Yes	Details →

All 19 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2019 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for nodeschnaps

Vulnerability	Severity	Fixed version ↑	Disclosed ↑
CVE-2016-10622: Insecure Download of Executable in nodeschnaps	N/A high	1.0.3	18 Feb 2019

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