Spectra Assure

failRisk: Vulnerabilities

Scanned:

Fortran Runner

Artifact:

latest

Top 10k

Run MINGW Fortran easily within Visual Studio Code! Auto-injects launch and tasks configuration for Fortran projects.

License: unknown

Published:

Publisher: RahilPrakash

Visit GitHub

See on Visual Studio Code

SAFE Assessment

Compliance

Licenses

1 copyleft licensed components

Secrets

No sensitive information found

Security

Vulnerabilities

3 severe vulnerabilities exploited

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

List of software quality issues with the number of affected components.

Policies

Info

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

548 packages

found in

Top 1k

3078 packages

found in

Top 10k

17.39k packages

in community

Next steps

We strongly advise updating 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

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. 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. Copyleft licenses in particular impose substantial restrictions on the licensee. They typically require that any derived works, and even software code that merely interacts with copyleft code, be licensed under the same license. Since copyleft licenses are commonly applied to open source code, their inclusion requires that the entire software package becomes open sourced. For commercial applications, this is typically undesirable. Therefore, the inclusion of copyleft code is commonly avoided or even prohibited by the organization policy.

Prevalence in Visual Studio Code community

7 packages

found in

Top 100

79 packages

found in

Top 1k

735 packages

found in

Top 10k

4.58k packages

in community

Next steps

Confirm that the software package includes a copyleft component.

Investigate if the software publisher provides this component under a non-copyleft license.

Consider replacing the software component with an alternative that offers a license compatible with commercial use.

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.

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 medium severity.

Prevalence in Visual Studio Code community

64 packages

found in

Top 100

530 packages

found in

Top 1k

2998 packages

found in

Top 10k

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

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, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in Visual Studio Code community

60 packages

found in

Top 100

434 packages

found in

Top 1k

2301 packages

found in

Top 10k

13.88k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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 low severity.

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

388 packages

found in

Top 1k

2065 packages

found in

Top 10k

10.51k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.

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 their reputation by being transparent. The person behind the public-facing alias is just as important as the alias itself. Developers rarely opt to use anonymous email service accounts that hide the link between their alias and the person behind it. Software components published by anonymized developer accounts often relate to activities that are unsuited for enterprise consumption.

Prevalence in Visual Studio Code community

28 packages

found in

Top 100

217 packages

found in

Top 1k

1339 packages

found in

Top 10k

6.41k packages

in community

Next steps

Investigate reported detections.

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

Consider replacing the software component with an alternative.

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.

List of software quality issues with the number of affected components.

Policies

Info

Problem

Prevalence in Visual Studio Code community

67 packages

found in

Top 100

548 packages

found in

Top 1k

3078 packages

found in

Top 10k

17.39k packages

in community

Next steps

We strongly advise updating 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

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

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

7 packages

found in

Top 100

79 packages

found in

Top 1k

735 packages

found in

Top 10k

4.58k packages

in community

Next steps

Confirm that the software package includes a copyleft component.

Investigate if the software publisher provides this component under a non-copyleft license.

Consider replacing the software component with an alternative that offers a license compatible with commercial use.

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.

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 medium severity.

Prevalence in Visual Studio Code community

64 packages

found in

Top 100

530 packages

found in

Top 1k

2998 packages

found in

Top 10k

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

60 packages

found in

Top 100

434 packages

found in

Top 1k

2301 packages

found in

Top 10k

13.88k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

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 low severity.

Prevalence in Visual Studio Code community

52 packages

found in

Top 100

388 packages

found in

Top 1k

2065 packages

found in

Top 10k

10.51k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update the component to the latest version.

Lower severity vulnerabilities can be resolved with less urgency, but you should still make a plan to do so.

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 their reputation by being transparent. The person behind the public-facing alias is just as important as the alias itself. Developers rarely opt to use anonymous email service accounts that hide the link between their alias and the person behind it. Software components published by anonymized developer accounts often relate to activities that are unsuited for enterprise consumption.

Prevalence in Visual Studio Code community

28 packages

found in

Top 100

217 packages

found in

Top 1k

1339 packages

found in

Top 10k

6.41k packages

in community

Next steps

Investigate reported detections.

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

Consider replacing the software component with an alternative.

Fortran Runner

SAFE Assessment

Compliance

Security

Threats

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

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

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

SQ12101Detected presence of software components distributed with copyleft licenses.Causes risk: copyleft licensed componentslicenses

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

SQ31106Detected presence of medium severity vulnerabilities.Causes risk: medium severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31107Detected presence of low severity vulnerabilities.Causes risk: low severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH15405Detected presence of software components authored by developers with anonymous email service accounts.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

Did you know...

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

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

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

SQ12101Detected presence of software components distributed with copyleft licenses.Causes risk: copyleft licensed componentslicenses

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

SQ31106Detected presence of medium severity vulnerabilities.Causes risk: medium severity vulnerabilitiesvulnerabilities

Problem

Prevalence in Visual Studio Code community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in Visual Studio Code community

Next steps

SQ31107Detected presence of low severity vulnerabilities.Causes risk: low severity vulnerabilitiesvulnerabilities

Problem