Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: about 7 hours ago

Open in Editor

Artifact:
latest
Top 10k
Open a file in Visual Studio, Atom Editor, Emacs, IntelliJ IDEA Community Edition, Sublime Text, PhpStorm, Vim, WebStorm or any other external editor from VS Code.
License: unknown
Published: over 7 years ago
Publisher: generalov
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

Popularity

13.39k
Total Installs
1
Contributor
1
Declared Dependencies
0
Dependents

Top issues

See all issues

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

12 packages
found in
Top 100
62 packages
found in
Top 1k
231 packages
found in
Top 10k
638 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.

Top behaviors

See all behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
83 packages
found in
Top 100
638 packages
found in
Top 1k
3956 packages
found in
Top 10k
23785 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
834 packages
found in
Top 1k
6690 packages
found in
Top 10k
83799 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
68 packages
found in
Top 100
480 packages
found in
Top 1k
2640 packages
found in
Top 10k
13864 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
67 packages
found in
Top 100
485 packages
found in
Top 1k
2974 packages
found in
Top 10k
17374 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
70 packages
found in
Top 100
553 packages
found in
Top 1k
3345 packages
found in
Top 10k
19620 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Open in Editor

What is Open in Editor?

Open a file in Visual Studio, Atom Editor, Emacs, IntelliJ IDEA Community Edition, Sublime Text, PhpStorm, Vim, WebStorm or any other external editor from VS Code.

Is Open in Editor malicious or is it safe to use?

The VS Code package Open in Editor 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 Open in Editor popular?

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

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