VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

algo-svnspawn: vulnerability history, versions and safety

algo-svnspawn is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 affected range, first recorded in Apr 2023. 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 C1
i
1 with no fix published

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

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all algo-svnspawn vulnerabilities

Vulert verdict on algo-svnspawn i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for algo-svnspawn is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Long-term outlook: risky 1 vulnerability on record across 1 year, none in the last year.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 26 Apr 2023 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 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.

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.

i
Affected range Vulnerabilities
all releases, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 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.

03 Vulnerabilities

Recorded vulnerabilities for algo-svnspawn

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious code in algo-svnspawn (npm) N/A critical No fix published 26 Apr 2023

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 algo-svnspawn

Is algo-svnspawn safe to use?

No. Vulert records a malicious-package vulnerability for algo-svnspawn: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

How many vulnerabilities does algo-svnspawn have?

1 vulnerability is recorded for algo-svnspawn 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 algo-svnspawn vulnerabilities disclosed?

0 vulnerabilities were recorded for algo-svnspawn in the last 12 months, and the oldest entry in this database dates to 26 Apr 2023. 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 algo-svnspawn 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor algo-svnspawn for upcoming vulnerabilities?

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