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

eventemitter2

latest
Top 10k
A feature-rich Node.js event emitter implementation with namespaces, wildcards, TTL, async listeners and browser/worker support.
License: Permissive (MIT)
Published: over 3 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

2.53B
Recorded Downloads Since 2021
Contributors
Declared Dependencies
2.45k
Dependents

Top issues

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 npm community

0 packages
found in
Top 100
2 packages
found in
Top 1k
36 packages
found in
Top 10k
2665 packages
in community

Next steps

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

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in npm community

0 packages
found in
Top 100
0 packages
found in
Top 1k
1 packages
found in
Top 10k
1375 packages
in community

Next steps

Investigate reported detections.
If the software intent does not relate to the reported behavior, 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 rewriting the flagged code without using the marked behaviors.

Top behaviors

Prevalence in npm community

No behavior prevalence information at this time

Prevalence in npm community

Behavior commonly used by malicious software (Important)
Behavior often found in this community (Common)
0 packages
found in
Top 100
2 packages
found in
Top 1k
36 packages
found in
Top 10k
2665 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
17 packages
found in
Top 100
159 packages
found in
Top 1k
1170 packages
found in
Top 10k
247753 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
71 packages
found in
Top 100
469 packages
found in
Top 1k
5346 packages
found in
Top 10k
1641704 packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
68 packages
found in
Top 100
385 packages
found in
Top 1k
4383 packages
found in
Top 10k
1965755 packages
in community

Top vulnerabilities

No vulnerabilities found.