Check your dependencies for malware and vulnerabilities without leaving VS Code

Meet Spectra Code, for free

Toolbox

Explore

Learn

ReversingLabs

Spectra Assure

Community

VS Code

Search by package name, PURL or hash

passEverything is awesome!

Scanned:

Salesforce Live Preview

Artifact:

latest

Top 10k

Salesforce Live Preview for Lightning Web Components

License: Permissive (BSD-3-Clause)

Published:

Publisher: salesforce

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Overview issues6 vulnerabilities0 malware0 behaviors192 dependencies0 contributors1 versions9

Popularity

133.89k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Software components are typically distributed in standardized packaging formats. Software packages are built from instructions written within package manifests that act as blueprints for package assembly. A package manifest declares the most important software properties, such as the package name, its authors and license, external dependencies, and various actions that may occur during the package lifecycle. Package managers are specialized tools used by developers to manage software components. Package managers read these manifests to deploy software components along with their dependencies. The premise of the package management system is that software components are isolated from each other, and that they rely on the package manager to provide their dependencies. However, it was detected that a software component includes code capable of accessing or modifying directories that are maintained exclusively by package managers. This is unusual as it resembles tactics used by threat actors that tamper with installed software components and inject malicious code into trusted execution paths.

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

540 packages

found in

Top 1k

3333 packages

found in

Top 10k

24.83k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

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 service 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 leverage the GitHub service to deliver malicious payloads.

Prevalence in Visual Studio Code community

84 packages

found in

Top 100

631 packages

found in

Top 1k

4538 packages

found in

Top 10k

42.23k 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 components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign on their own, some might become important for analysis when observed alongside other capabilities the component exhibits. This issue is reported for files that can enumerate user information and make HTTP requests. While presence of this behavior combination does not imply malicious intent, it is advised that the reported files are reviewed. One example of acceptable use for this type of data collection is the opt-in telemetry for software debugging purposes.

Prevalence in Visual Studio Code community

31 packages

found in

Top 100

164 packages

found in

Top 1k

505 packages

found in

Top 10k

2.82k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in Visual Studio Code community

54 packages

found in

Top 100

470 packages

found in

Top 1k

3482 packages

found in

Top 10k

70.97k 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

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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

72 packages

found in

Top 100

515 packages

found in

Top 1k

2732 packages

found in

Top 10k

21.26k 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 changing the port to one that is standard for the networking protocol.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

33 packages

found in

Top 100

179 packages

found in

Top 1k

547 packages

found in

Top 10k

3.25k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

72 packages

found in

Top 100

573 packages

found in

Top 1k

3196 packages

found in

Top 10k

21.88k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

32 packages

found in

Top 100

176 packages

found in

Top 1k

508 packages

found in

Top 10k

3.01k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

79 packages

found in

Top 100

540 packages

found in

Top 1k

3358 packages

found in

Top 10k

25.05k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

49 packages

found in

Top 100

337 packages

found in

Top 1k

1756 packages

found in

Top 10k

10.32k packages

in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Salesforce Live Preview

What is Salesforce Live Preview?

Salesforce Live Preview for Lightning Web Components. For more information about this package, visit its homepage.

Is Salesforce Live Preview malicious or is it safe to use?

The VS Code package Salesforce Live Preview was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is Salesforce Live Preview popular?

The VS Code package Salesforce Live Preview ranks among the top 10000 projects in this community. It has 134K 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 Salesforce Live Preview once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how Salesforce Live Preview behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a Salesforce Live Preview 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.

Popularity

133.89k

Total Installs

Contributor

Declared Dependencies

Dependents

Top issues

See all issues

Problem

Prevalence in Visual Studio Code community

79 packages

found in

Top 100

540 packages

found in

Top 1k

3333 packages

found in

Top 10k

24.83k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1554 - Compromise Host Software Binary.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in Visual Studio Code community

84 packages

found in

Top 100

631 packages

found in

Top 1k

4538 packages

found in

Top 10k

42.23k 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

31 packages

found in

Top 100

164 packages

found in

Top 1k

505 packages

found in

Top 10k

2.82k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1033 - System Owner/User Discovery.

Consider limiting the collection of user information to a minimum.

Problem

Prevalence in Visual Studio Code community

54 packages

found in

Top 100

470 packages

found in

Top 1k

3482 packages

found in

Top 10k

70.97k 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

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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

72 packages

found in

Top 100

515 packages

found in

Top 1k

2732 packages

found in

Top 10k

21.26k 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 changing the port to one that is standard for the networking protocol.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

33 packages

found in

Top 100

179 packages

found in

Top 1k

547 packages

found in

Top 10k

3.25k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

72 packages

found in

Top 100

573 packages

found in

Top 1k

3196 packages

found in

Top 10k

21.88k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

32 packages

found in

Top 100

176 packages

found in

Top 1k

508 packages

found in

Top 10k

3.01k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

79 packages

found in

Top 100

540 packages

found in

Top 1k

3358 packages

found in

Top 10k

25.05k packages

in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)

49 packages

found in

Top 100

337 packages

found in

Top 1k

1756 packages

found in

Top 10k

10.32k packages

in community

Top vulnerabilities

No vulnerabilities found.

Salesforce Live Preview

SAFE Assessment

Compliance

Security

Threats

Popularity

Top issues

TH16129Detected presence of software components that can tamper with other installed software.hunting

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

TH16106Detected presence of files that collect and exfiltrate user information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Reads from version control configuration files.steal

Prevalence in Visual Studio Code community

Modifies file/directory permissions.permissions

Prevalence in Visual Studio Code community

Writes to version control configuration files.file

Prevalence in Visual Studio Code community

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Changes file ownership.file

Prevalence in Visual Studio Code community

Top vulnerabilities

FAQ for Salesforce Live Preview

What is Salesforce Live Preview?

Is Salesforce Live Preview malicious or is it safe to use?

Is Salesforce Live Preview popular?

How do I secure Salesforce Live Preview once it is in my app?

Did you know...

Popularity

Top issues

TH16129Detected presence of software components that can tamper with other installed software.hunting

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

TH16106Detected presence of files that collect and exfiltrate user information.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

TH17115Detected presence of files containing URLs that use non-standard ports.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Top behaviors

Reads from version control configuration files.steal

Prevalence in Visual Studio Code community

Modifies file/directory permissions.permissions

Prevalence in Visual Studio Code community

Writes to version control configuration files.file

Prevalence in Visual Studio Code community

Writes to directories managed by package managers.file

Prevalence in Visual Studio Code community

Changes file ownership.file

Prevalence in Visual Studio Code community

Top vulnerabilities