Spectra Assure
Community
Docs
warningRisk: Vulnerabilities
Scanned: 13 days ago

blessed

latest
Top 10k
A high-level terminal interface library for node.js.
License: Permissive (MIT)
Published: over 10 years ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
2 medium severity vulnerabilities
Hardening
No application hardening issues

Threats

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

Popularity

321.34M
Recorded Downloads Since 2021
Contributor
Declared Dependencies
1.72k
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 npm community

10 packages
found in
Top 100
52 packages
found in
Top 1k
959 packages
found in
Top 10k
183909 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

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as medium severity.

Prevalence in npm community

21 packages
found in
Top 100
132 packages
found in
Top 1k
2542 packages
found in
Top 10k
965123 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

Prevalence in npm community

Behavior often found in this community (Common)
21 packages
found in
Top 100
136 packages
found in
Top 1k
1248 packages
found in
Top 10k
390529 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
10 packages
found in
Top 100
52 packages
found in
Top 1k
959 packages
found in
Top 10k
183924 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
5 packages
found in
Top 100
39 packages
found in
Top 1k
518 packages
found in
Top 10k
107169 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
15 packages
found in
Top 100
90 packages
found in
Top 1k
1202 packages
found in
Top 10k
290629 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
15 packages
found in
Top 100
51 packages
found in
Top 1k
596 packages
found in
Top 10k
137110 packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(2 Active Vulnerabilities)
None
2 (1 Fixable)
CVE-2023-28155m
CVE-2017-16026m
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated