Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: about 12 hours ago

Devdock - World's first Web3 Development Agent

Artifact:
latest
Top 10k
World's First Developer copilot that rewards you for every line of code.
License: Permissive (Apache-2.0)
Published: about 2 months ago

Publisher: agent



SAFE Assessment

Compliance

Licenses
1 patent license considerations
Secrets
1 web service credentials found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
1 components with malware history
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

9.13k
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

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 specify that a separate agreement may be required for the use of patents the code may be leveraging. Patents are granted for significant innovations, and their use is typically tied to monetary compensation. When building commercial applications, this may be undesirable. Therefore, the inclusion of any patent-protected code is commonly scrutinized and often prohibited by the organization policy.

Prevalence in Visual Studio Code community

3 packages
found in
Top 100
16 packages
found in
Top 1k
85 packages
found in
Top 10k
494 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 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 as a Service (SaaS) platforms expose programmable interfaces to their authenticated users. These web services enable action automation and secure exchange of information. For authorization, web service users provide a unique token that confirms their access rights. These tokens are considered secrets. They should never be included in a software release package, even if they are obfuscated by encryption on the client-side.

Prevalence in Visual Studio Code community

3 packages
found in
Top 100
34 packages
found in
Top 1k
71 packages
found in
Top 10k
457 packages
in community

Next steps

You should securely store web service access tokens, and fully automate their management and periodic rotation.
If tokens were published unintentionally and the software has been made public, you should revoke exposed tokens and file a security incident.
Examples of service tokens that may have been detected include AWS, Facebook, JWT, SWT, Slack and others.

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.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
53 packages
found in
Top 100
331 packages
found in
Top 1k
1160 packages
found in
Top 10k
5.29k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
67 packages
found in
Top 100
547 packages
found in
Top 1k
2891 packages
found in
Top 10k
14.99k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
74 packages
found in
Top 100
578 packages
found in
Top 1k
3262 packages
found in
Top 10k
18.65k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
48 packages
found in
Top 100
302 packages
found in
Top 1k
1663 packages
found in
Top 10k
8.56k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
79 packages
found in
Top 100
622 packages
found in
Top 1k
4233 packages
found in
Top 10k
29.36k packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(1 Active Vulnerabilities)
None
1 (1 Fixable)
CVE-2025-47934h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated