Spectra Assure
Community
passEverything is awesome!
Scanned: 12 days ago

@nevware21/ts-async

latest
support for asynchronous development with a Promise based task Scheduler, several different Promise implementations (synchronous, idle, asynchronous and native runtime wrappers), await helpers, and aliases all built and tested using TypeScript.
License: Permissive (MIT)
Published: about 1 year 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

35.66M
Recorded Downloads Since 2021
Contributors
Declared Dependencies
18
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
53 packages
found in
Top 1k
981 packages
found in
Top 10k
194.82k 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 npm community

Behavior often found in this community (Common)
10 packages
found in
Top 100
53 packages
found in
Top 1k
981 packages
found in
Top 10k
194.83k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
15 packages
found in
Top 100
49 packages
found in
Top 1k
893 packages
found in
Top 10k
104.96k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
13 packages
found in
Top 100
59 packages
found in
Top 1k
1107 packages
found in
Top 10k
472.06k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
40 packages
found in
Top 100
305 packages
found in
Top 1k
3796 packages
found in
Top 10k
1.13M packages
in community

Top vulnerabilities

No vulnerabilities found.