Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 7 days ago

xhr2

latest
Top 10k
XMLHttpRequest emulation for node.js
License: Permissive (MIT)
Published: almost 5 years ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

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

Popularity

180.21M
Recorded Downloads Since 2021
Contributor
Declared Dependencies
1.07k
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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in npm community

6 packages
found in
Top 100
41 packages
found in
Top 1k
869 packages
found in
Top 10k
490844 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 changing the port to one that is standard for the networking protocol.

Problem

Private keys and certificates are considered sensitive information that should not be included in released software packages. However, developers frequently release sensitive information alongside their applications to facilitate automated software testing. Testing keys and certificates often proliferate through the software supply chain. When such information gets shared publicly, it is catalogued by file reputation databases. Any private key and certificate files seen by a file reputation database prior to configured time threshold can be automatically suppressed. Commonly shared sensitive information is not considered to be secret.

Prevalence in npm community

3 packages
found in
Top 100
25 packages
found in
Top 1k
336 packages
found in
Top 10k
63841 packages
in community

Next steps

Review the commonly shared sensitive information for evidence of inadvertently exposed secrets.
If the keys were published unintentionally and the software has been made public, you should revoke the keys and file a security incident.

Top behaviors

Prevalence in npm community

No behavior prevalence information at this time

Prevalence in npm community

Behavior often found in this community (Common)
6 packages
found in
Top 100
41 packages
found in
Top 1k
869 packages
found in
Top 10k
491126 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
2 packages
found in
Top 100
17 packages
found in
Top 1k
205 packages
found in
Top 10k
44587 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
3 packages
found in
Top 100
19 packages
found in
Top 1k
382 packages
found in
Top 10k
51812 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
7 packages
found in
Top 100
52 packages
found in
Top 1k
886 packages
found in
Top 10k
616361 packages
in community

Top vulnerabilities

No vulnerabilities found.