Spectra Assure
Community
Docs
warningRisk: Tampering
Scanned: 2 days ago

Go

Artifact:
latest
key project
Top 100
Rich Go language support for Visual Studio Code
License: Permissive (MIT)
Published: 15 days ago
Publisher: golang
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
1 components with malware history
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

17.14M
Total Installs
1
Contributor
12
Declared Dependencies
17
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. Some open source projects have a history of security lapses that culminated with a publication of one or more malicious component versions. To ensure that repeated supply chain incidents do not occur, the open source project should be closely monitored for up to two years. All software package versions that are published within two years of the malware incident will convey a warning about the history of security incidents tied to the open source project.

Prevalence in Visual Studio Code community

24 packages
found in
Top 100
102 packages
found in
Top 1k
326 packages
found in
Top 10k
1057 packages
in community

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
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)
85 packages
found in
Top 100
673 packages
found in
Top 1k
4329 packages
found in
Top 10k
28768 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
81 packages
found in
Top 100
631 packages
found in
Top 1k
3887 packages
found in
Top 10k
24357 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
73 packages
found in
Top 100
573 packages
found in
Top 1k
3170 packages
found in
Top 10k
17492 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
76 packages
found in
Top 100
599 packages
found in
Top 1k
3178 packages
found in
Top 10k
16700 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
47 packages
found in
Top 100
303 packages
found in
Top 1k
1634 packages
found in
Top 10k
8176 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for Go

What is Go?

Rich Go language support for Visual Studio Code. For more information about this package, visit its homepage.

Is Go malicious or is it safe to use?

The VS Code package Go was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to download and use. 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. The package Go had 25 incidents in versions published within 2 years prior to the latest.

Is Go popular?

The VS Code package Go is classified as a key project because of its widespread usage and impact. Go ranks among the top 100 projects in the VS Code community. It has 17M 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 Go once it is in my app?

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