Spectra Assure
Community
Docs
warningRisk: Secrets
Scanned: 8 days ago

IntelliCode for C# Dev Kit

Artifact:
latest
Top 1k
AI-assisted development for C# Dev Kit
License: unknown
Published: about 1 year ago

Publisher: ms-dotnettools



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
4 debugging symbols found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
2 outdated toolchains detected

Threats

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

Popularity

4.21M
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

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

78 packages
found in
Top 100
618 packages
found in
Top 1k
4203 packages
found in
Top 10k
27868 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

Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The United States Government has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Cuba (.cu), Iran (.ir), North Korea (.nk) and Syria (.sy).

Prevalence in Visual Studio Code community

7 packages
found in
Top 100
34 packages
found in
Top 1k
77 packages
found in
Top 10k
338 packages
in community

Next steps

Investigate reported detections.
You should delay the software release until the legal review is completed.

Problem

Export restrictions (or a restriction on exportation) are limitations on the quantity of goods exported to a specific country or countries by a Government. The European Union has imposed export restrictions on a number of countries and regions. These restrictions may or may not apply to digital goods such as software and other related intellectual property. It is advised that the reported findings are put in the usage context so that they can be audited and reviewed by the legal department before the software package is deployed. Current list of countries with export restrictions includes: Belarus (.by), Iran (.ir), Iraq (.iq), Libya (.ly), Myanmar (.mm), North Korea (.nk), Syria (.sy), Venezuela (.ve) and Zimbabwe (.zw).

Prevalence in Visual Studio Code community

12 packages
found in
Top 100
78 packages
found in
Top 1k
224 packages
found in
Top 10k
975 packages
in community

Next steps

Investigate reported detections.
You should delay the software release until the legal review is completed.

Problem

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.

Prevalence in Visual Studio Code community

38 packages
found in
Top 100
250 packages
found in
Top 1k
719 packages
found in
Top 10k
3448 packages
in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

Problem

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors. These checks prevent the use of hard-to-secure memory manipulation functions. They enforce static memory access checks, and allow only the use of range-verified memory access functions. While these checks do not prevent every memory corruption issue by themselves, they do help reduce the likelihood.

Prevalence in Visual Studio Code community

23 packages
found in
Top 100
125 packages
found in
Top 1k
203 packages
found in
Top 10k
813 packages
in community

Next steps

It's highly recommended to enable these checks for all software components used at security boundaries, or those that process user controlled inputs.
To enable these checks, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

Top behaviors

Prevalence in Visual Studio Code community

Behavior uncommon for this community (Uncommon)
4 packages
found in
Top 100
14 packages
found in
Top 1k
40 packages
found in
Top 10k
149 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
21 packages
found in
Top 100
135 packages
found in
Top 1k
319 packages
found in
Top 10k
1413 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
65 packages
found in
Top 100
535 packages
found in
Top 1k
2853 packages
found in
Top 10k
14133 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
28 packages
found in
Top 100
169 packages
found in
Top 1k
418 packages
found in
Top 10k
1486 packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
23 packages
found in
Top 100
139 packages
found in
Top 1k
333 packages
found in
Top 10k
1311 packages
in community

Top vulnerabilities

No vulnerabilities found.