warningRisk: Vulnerabilities

Scanned:

⚡ Modern Live Server Pro

Artifact:

latest

Next-generation live server with instant reload, WebSocket sync, and zero-config setup. Perfect for modern web development with React, Vue, or vanilla HTML/CSS/JS projects.

License: unknown

Published:

Publisher: Shellomo

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

1 software distribution restrictions

Secrets

No sensitive information found

Security

Vulnerabilities

2 high severity vulnerabilities

Hardening

2 execution hijacking concerns

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Popularity

8.8k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in Visual Studio Code community

68 packages

found in

Top 100

555 packages

found in

Top 1k

3086 packages

found in

Top 10k

17.47k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to raw files hosted on GitHub. Attackers often abuse popular web services to host malicious payloads. Since code-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of code-sharing service locations does not imply malicious intent, all of their uses in a software package should be documented and approved. An increasing number of software supply chain attacks in the open source space leverages the GitHub service to deliver malicious payloads.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Software developers publish components they have authored to public repositories. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in Visual Studio Code community

25 packages

found in

Top 100

151 packages

found in

Top 1k

793 packages

found in

Top 10k

3.71k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Each of these components can have dozens, or even hundreds, of its own dependencies. When building applications, software developers download and install components from public repositories. For components to work properly, all of their dependencies also need to be installed. Some package repositories, like Node Package Manager (NPM), allow components to declare dependencies that are hosted remotely. Such dependencies are automatically downloaded from a specified location during software component installation. Since remotely hosted dependencies are not immutable, that enables a threat actor to change the dependency contents even after a component was published and vetted by security solutions. It is uncommon to find open source components that use remotely hosted dependencies residing outside the official project source code repository.

Prevalence in Visual Studio Code community

36 packages

found in

Top 100

227 packages

found in

Top 1k

1175 packages

found in

Top 10k

5.7k packages

in community

Next steps

Review software component remote dependency locations.

If the software component resolves dependencies from unusual locations, investigate the build and release environment for software supply chain compromise.

Consider vendoring the software component with all of its dependencies.

Avoid using this software package until it is vetted as safe.

Problem

Software license is a legal instrument that governs the use and distribution of software source code and its binary representation. Software publishers have the freedom to choose any commonly used or purposefully written license to publish their work under. While some licenses are liberal and allow almost any kind of distribution, with or without code modification, other licenses are more restrictive and impose rules for their inclusion in other software projects. Some software licenses place restrictions on software distribution of the code they apply to. These restrictions may extend to the services built upon the code licensed under such restrictive licenses. Some restrictive licenses explicitly state that the licensee may not provide the software to third parties as a hosted or managed service, where the service provides users with access to any substantial set of the features or functionality of the licensed software. When building commercial applications, this is typically undesirable. Therefore, the inclusion of any code that may impose limits on software distribution is commonly avoided or even prohibited by the organization policy.

Prevalence in Visual Studio Code community

34 packages

found in

Top 100

245 packages

found in

Top 1k

1626 packages

found in

Top 10k

8.95k packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

84 packages

found in

Top 100

679 packages

found in

Top 1k

4393 packages

found in

Top 10k

30.42k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

82 packages

found in

Top 100

636 packages

found in

Top 1k

3971 packages

found in

Top 10k

25.82k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

74 packages

found in

Top 100

578 packages

found in

Top 1k

3262 packages

found in

Top 10k

18.65k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

54 packages

found in

Top 100

378 packages

found in

Top 1k

1783 packages

found in

Top 10k

7.78k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

77 packages

found in

Top 100

612 packages

found in

Top 1k

3282 packages

found in

Top 10k

18.03k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(4 Active Vulnerabilities)

4 (4 Fixable)

CVE-2025-15284h

CVE-2024-52798h

CVE-2026-2391m

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

FAQ for ⚡ Modern Live Server Pro

What is ⚡ Modern Live Server Pro?

Next-generation live server with instant reload, WebSocket sync, and zero-config setup. Perfect for modern web development with React, Vue, or vanilla HTML/CSS/JS projects. For more information about this package, visit its homepage.

Is ⚡ Modern Live Server Pro malicious or is it safe to use?

The VS Code package ⚡ Modern Live Server Pro was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. The package contains risks, and the analysis results should be reviewed before it is downloaded and used. Visit the Issues and Behaviors sections of the analysis for more details.

Is ⚡ Modern Live Server Pro popular?

The VS Code package ⚡ Modern Live Server Pro ranks among the top 10000 projects in this community. It has 9K recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure ⚡ Modern Live Server Pro once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how ⚡ Modern Live Server Pro behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a ⚡ Modern Live Server Pro version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

Popularity

8.8k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.

Prevalence in Visual Studio Code community

68 packages

found in

Top 100

555 packages

found in

Top 1k

3086 packages

found in

Top 10k

17.47k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

622 packages

found in

Top 1k

4233 packages

found in

Top 10k

29.36k packages

in community

Next steps

Investigate reported detections.

If the software should not include these network references, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider an alternative delivery mechanism for software packages.

Problem

Prevalence in Visual Studio Code community

25 packages

found in

Top 100

151 packages

found in

Top 1k

793 packages

found in

Top 10k

3.71k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Each of these components can have dozens, or even hundreds, of its own dependencies. When building applications, software developers download and install components from public repositories. For components to work properly, all of their dependencies also need to be installed. Some package repositories, like Node Package Manager (NPM), allow components to declare dependencies that are hosted remotely. Such dependencies are automatically downloaded from a specified location during software component installation. Since remotely hosted dependencies are not immutable, that enables a threat actor to change the dependency contents even after a component was published and vetted by security solutions. It is uncommon to find open source components that use remotely hosted dependencies residing outside the official project source code repository.

Prevalence in Visual Studio Code community

36 packages

found in

Top 100

227 packages

found in

Top 1k

1175 packages

found in

Top 10k

5.7k packages

in community

Next steps

Review software component remote dependency locations.

If the software component resolves dependencies from unusual locations, investigate the build and release environment for software supply chain compromise.

Consider vendoring the software component with all of its dependencies.

Avoid using this software package until it is vetted as safe.

Problem

Prevalence in Visual Studio Code community

34 packages

found in

Top 100

245 packages

found in

Top 1k

1626 packages

found in

Top 10k

8.95k packages

in community

Next steps

Confirm that the software package references a component or a dependency with a restrictive license.

Consider replacing the software component with an alternative that offers a license compatible with organization policy.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

84 packages

found in

Top 100

679 packages

found in

Top 1k

4393 packages

found in

Top 10k

30.42k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

82 packages

found in

Top 100

636 packages

found in

Top 1k

3971 packages

found in

Top 10k

25.82k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

74 packages

found in

Top 100

578 packages

found in

Top 1k

3262 packages

found in

Top 10k

18.65k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

54 packages

found in

Top 100

378 packages

found in

Top 1k

1783 packages

found in

Top 10k

7.78k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

77 packages

found in

Top 100

612 packages

found in

Top 1k

3282 packages

found in

Top 10k

18.03k packages

in community

Top vulnerabilities

See all vulnerabilities

Vulnerability Exploitation Lifecycle

(4 Active Vulnerabilities)

4 (4 Fixable)

CVE-2025-15284h

CVE-2024-52798h

CVE-2026-2391m

None

Exploits Unknown

Exploits Exist

Exploited by Malware

Patching Mandated

⚡ Modern Live Server Pro

SAFE Assessment

Compliance

Security

Threats

Popularity

Top issues

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30109Detected presence of software components with dependencies that are hosted outside the official project repository.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ12405Detected presence of licenses that place restrictions on software distribution.Causes risk: software distribution restrictionslicenses

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Decodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Contains a sequence of bytes that can be decoded into a printable string.packer

Prevalence in Visual Studio Code community

Opens a TCP connection to a remote server.network

Prevalence in Visual Studio Code community

Top vulnerabilities

FAQ for ⚡ Modern Live Server Pro

What is ⚡ Modern Live Server Pro?

Is ⚡ Modern Live Server Pro malicious or is it safe to use?

Is ⚡ Modern Live Server Pro popular?

How do I secure ⚡ Modern Live Server Pro once it is in my app?

Did you know...

Popularity

Top issues

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH17127Detected presence of files containing URLs that link to raw files on GitHub.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30106Detected presence of software components that have low popularity or number of downloads.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30109Detected presence of software components with dependencies that are hosted outside the official project repository.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ12405Detected presence of licenses that place restrictions on software distribution.Causes risk: software distribution restrictionslicenses

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Might contain potentially obfuscated code or data.anomaly

Prevalence in Visual Studio Code community

Encodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Decodes data using the Base64 algorithm.packer

Prevalence in Visual Studio Code community

Contains a sequence of bytes that can be decoded into a printable string.packer

Prevalence in Visual Studio Code community

Opens a TCP connection to a remote server.network

Prevalence in Visual Studio Code community

Top vulnerabilities