Is ripmed160 safe to use?

Vulert records 1 vulnerabilities for ripmed160 in npm: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does ripmed160 have?

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

0 vulnerabilities were recorded for ripmed160 in the last 12 months, and the oldest entry in this database dates to 03 Sep 2020. 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 ripmed160 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 ripmed160 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the ripmed160 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

ripmed160: vulnerability history, versions and safety

ripmed160 is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 affected range, first recorded in Sep 2020. 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 C1

1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →

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

Vulert verdict on ripmed160 i

Updated on 23 Oct 2026

Careful: one of the 1 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 1 vulnerability on record across 1 year, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Vulnerabilities on record 1 over 1 year · 0 in the last year i
Latest disclosure 03 Sep 2020 i
Highest CVSS 9.1 i
With no published fix 1 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

Affected range	Vulnerabilities
from 0.0.0 onwards, no fix published yet	1

02 Disclosure history

How often vulnerabilities are recorded

2020 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 ripmed160

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Malicious Package in ripmed160	9.1 critical	No fix published	03 Sep 2020

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