Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 5 days ago

EmmyLuaCodeStyle

Artifact:
latest
Top 10k
reformat lua code and lint lua code style
License: unknown
Published: over 1 year ago

Publisher: CppCXY



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
1 low priority mitigations absent

Threats

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

Popularity

9.07k
Total Installs
Contributor
Declared Dependencies
1
Dependents

Top issues

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

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. While a new software project is a welcome addition to the open source community, it is not always prudent to indiscriminately use the latest components when building a commercial application. Irrespective of the software quality, the danger of being the first to try out a new project lies in the fact that the software component may contain novel, currently undetected malicious code. Therefore, it is prudent to review software component behaviors and even try out software component in a sandbox, an environment meant for testing untrusted code.

Prevalence in Visual Studio Code community

25 packages
found in
Top 100
151 packages
found in
Top 1k
793 packages
found in
Top 10k
3.71k packages
in community

Next steps

Check the software component behaviors for anomalies.
Consider exploratory software component testing within a sandbox environment.
Consider replacing the software component with a more widely used alternative.
Avoid using this software package until it is vetted as safe.

Problem

Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that indirect calls are made only to vetted functions. This mitigation protects dynamically resolved function targets by instrumenting the code responsible for transferring execution control. Higher-level programming languages implement structured exception handling by managing their own code flow execution paths. As such, they are subject to code flow hijacking during runtime. Language-specific exception handling mitigation enforces execution integrity by instrumenting calls to manage execution context switching. Any deviation from the known and trusted code flow paths will cause the application to terminate. This makes malicious code less likely to execute.

Prevalence in Visual Studio Code community

47 packages
found in
Top 100
286 packages
found in
Top 1k
912 packages
found in
Top 10k
4.37k packages
in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.
To enable this mitigation, refer to your programming language toolchain documentation.
In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

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.

Top behaviors

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)
84 packages
found in
Top 100
679 packages
found in
Top 1k
4393 packages
found in
Top 10k
30.42k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
94 packages
found in
Top 100
837 packages
found in
Top 1k
6746 packages
found in
Top 10k
87.76k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
84 packages
found in
Top 100
661 packages
found in
Top 1k
3774 packages
found in
Top 10k
22.06k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
42 packages
found in
Top 100
215 packages
found in
Top 1k
589 packages
found in
Top 10k
2.53k packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2022-25883h
CVE-2025-5889l
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated