VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

orejime: vulnerability history, versions and safety

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

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 19 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all orejime vulnerabilities

Vulert verdict on orejime 3.2.1 i

Updated on 23 Oct 2026

Good news: 3.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 77/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 3.2.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 19 Dec 2025 i
  • Highest CVSS 1.7 i
  • With no published fix 0 i
  • Stars 190 i
  • Last release 2 months ago i
  • Licence BSD-3-Clause 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 orejime, 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
3.2.1 03 Aug 2026 none BSD-3-Clause — Details →
3.2.0 23 Jun 2026 none BSD-3-Clause — Details →
3.1.2-alpha.0 06 Mar 2026 none BSD-3-Clause — Details →
3.1.1 02 Mar 2026 none BSD-3-Clause — Details →
2.3.3 05 Feb 2026 none BSD-3-Clause — Details →
2.3.3-alpha.1 03 Feb 2026 none BSD-3-Clause — Details →
2.3.3-alpha.0 02 Feb 2026 none BSD-3-Clause — Details →
3.1.0 09 Jan 2026 none BSD-3-Clause — Details →
2.3.2 18 Dec 2025 none BSD-3-Clause — Details →
2.3.2-alpha.0 16 Dec 2025 L1 BSD-3-Clause Yes Details →
3.0.2 10 Jul 2025 none BSD-3-Clause — Details →
3.0.1 24 Apr 2025 none BSD-3-Clause — Details →
3.1.0-alpha.0 11 Mar 2025 none BSD-3-Clause — Details →
3.0.0 25 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.12 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.11 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.10 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.9 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.8 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.7 11 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.6 10 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.5 07 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.4 07 Feb 2025 none BSD-3-Clause — Details →
3.0.0-alpha.3 07 Feb 2025 none BSD-3-Clause — Details →
2.3.1 08 Oct 2024 L1 BSD-3-Clause Yes Details →
3.0.0-alpha.2 13 Sep 2024 none BSD-3-Clause — Details →
3.0.0-alpha.1 13 Sep 2024 none BSD-3-Clause — Details →
3.0.0-alpha.0 12 Sep 2024 none BSD-3-Clause — Details →
2.3.0 16 Aug 2023 L1 BSD-3-Clause Yes Details →
2.2.1 03 Mar 2022 L1 BSD-3-Clause Yes Details →
2.2.0 01 Mar 2022 L1 BSD-3-Clause Yes Details →
2.2.0-alpha.0 01 Mar 2022 L1 BSD-3-Clause Yes Details →
2.1.1 24 Sep 2021 L1 BSD-3-Clause Yes Details →
2.1.0 27 Aug 2021 L1 BSD-3-Clause Yes Details →
2.0.3 22 Apr 2021 L1 BSD-3-Clause Yes Details →
2.0.2 08 Apr 2021 L1 BSD-3-Clause Yes Details →
2.0.1 18 Feb 2021 L1 BSD-3-Clause Yes Details →
2.0.0 15 Feb 2021 L1 BSD-3-Clause Yes Details →
1.2.4 08 Dec 2020 L1 BSD-3-Clause Yes Details →
1.2.3 17 Feb 2020 L1 BSD-3-Clause Yes Details →
1.2.2 17 Feb 2020 L1 BSD-3-Clause Yes Details →
1.2.1 05 Feb 2020 L1 BSD-3-Clause Yes Details →
1.2.0 02 Dec 2019 L1 BSD-3-Clause Yes Details →
1.1.1 08 Apr 2019 L1 BSD-3-Clause Yes Details →
1.0.3 06 Feb 2019 L1 BSD-3-Clause Yes Details →
1.0.2 16 Jan 2019 L1 BSD-3-Clause Yes Details →
1.0.1 11 Dec 2018 L1 BSD-3-Clause Yes Details →
1.0.0 04 Dec 2018 L1 BSD-3-Clause Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for orejime

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-68457: Orejime Executable Code in HTML Attributes Vulnerability 1.7 low 2.3.2 19 Dec 2025

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 orejime

Is orejime safe to use?

Vulert records 1 vulnerabilities for orejime in npm: 0 critical, 0 high, 0 medium and 1 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 orejime's Vulert package health score?

Vulert scores orejime 77/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 orejime affected?

No. 3.2.1, 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 orejime should I use?

3.2.1 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 orejime have?

1 vulnerability is recorded for orejime in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new orejime vulnerabilities disclosed?

1 vulnerability was recorded for orejime in the last 12 months, and the oldest entry in this database dates to 19 Dec 2025. 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 orejime 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 orejime for upcoming vulnerabilities?

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