Spectra Assure
Community
Docs
passEverything is awesome!
Scanned: 1 day ago

expo

latest
Top 10k
The Expo SDK
License: Permissive (MIT)
New!
Published: 1 day 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

137.21M
Recorded Downloads Since 2021
Contributors
Declared Dependencies
5.74k
Dependents

Top issues

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. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in npm community

No prevalence information at this time

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

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

Behavior often found in this community (Common)
1 packages
found in
Top 100
5 packages
found in
Top 1k
150 packages
found in
Top 10k
29118 packages
in community

Prevalence in npm community

Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
17 packages
found in
Top 10k
10527 packages
in community

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)
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

No behavior prevalence information at this time

Top vulnerabilities

No vulnerabilities found.