Spectra Assure
Community
Docs
failRisk: Vulnerabilities
Scanned: 1 day ago

Cody

Artifact:
latest
Top 10k
Cody: your code assistant for Visual Studio Code
License: unknown
Published: over 1 year ago
Publisher: neuralgeeks
See on Visual Studio Code

SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 patch mandated vulnerabilities
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

53.59k
Total Installs
1
Contributor
8
Declared Dependencies
0
Dependents

Top issues

See all issues

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Regulatory body or a government agency has issued a patching mandate for all software components affected by the identified vulnerabilities.

Prevalence in Visual Studio Code community

14 packages
found in
Top 100
115 packages
found in
Top 1k
610 packages
found in
Top 10k
2379 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 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

71 packages
found in
Top 100
568 packages
found in
Top 1k
3198 packages
found in
Top 10k
16595 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. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.

Prevalence in Visual Studio Code community

27 packages
found in
Top 100
206 packages
found in
Top 1k
910 packages
found in
Top 10k
3803 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 critical severity.

Prevalence in Visual Studio Code community

64 packages
found in
Top 100
445 packages
found in
Top 1k
2064 packages
found in
Top 10k
9214 packages
in community

Next steps

Perform impact analysis for the reported CVEs.
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

72 packages
found in
Top 100
583 packages
found in
Top 1k
3344 packages
found in
Top 10k
17282 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.

Top behaviors

See all behaviors

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)
82 packages
found in
Top 100
656 packages
found in
Top 1k
3694 packages
found in
Top 10k
21768 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
84 packages
found in
Top 100
625 packages
found in
Top 1k
3822 packages
found in
Top 10k
24018 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
82 packages
found in
Top 100
643 packages
found in
Top 1k
4790 packages
found in
Top 10k
66215 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
88 packages
found in
Top 100
720 packages
found in
Top 1k
5373 packages
found in
Top 10k
72247 packages
in community

Top vulnerabilities

See all vulnerabilities
Vulnerability Exploitation Lifecycle
(12 Active Vulnerabilities)
9 (9 Fixable)
CVE-2022-29247c
CVE-2021-39184h
CVE-2023-29198h
3 (2 Fixable)
CVE-2020-7627c
CVE-2023-5217h
CVE-2025-55305m
1 (1 Fixable)
CVE-2023-5217h
1 (1 Fixable)
CVE-2023-5217h
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated

FAQ for Cody

What is Cody?

Cody: your code assistant for Visual Studio Code. For more information about this package, visit its homepage.

Is Cody malicious or is it safe to use?

The VS Code package Cody 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 Cody popular?

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

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