Spectra Assure
Community
Docs
failIncident: Removal
Scanned: 12 days ago

narwhals

Artifact:
removed
Top 1k
Extremely lightweight compatibility layer between dataframe libraries
License: Permissive (MIT)
Published: 5 months ago
Visit Github
See on PyPI

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
1 components prone to hijacking
Malware
No evidence of malware inclusion

INCIDENTS:

removal
Reported By: Community

Popularity

333.99M
Total Downloads
0
Contributors
14
Declared Dependencies
179
Dependents

Top issues

See all 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. Software developers publish components they have authored to public repositories. Open source projects are the intellectual property of their respective authors. At any time, the authors may choose to completely remove the software component from a public repository. This often occurs when a software project reaches its end-of-life stage, or when the software authors lose interest in maintaining the project. This kind of removal frees up the software package name, its unique software identifier in the public repository, for other developers to use. However, new software project owners might have malicious intent. Threat actors are continuously monitoring popular package names in case their unique identifiers suddenly become available for hijacking. Once the software projects falls under new ownership, the new maintainers may opt to use the project popularity to spread malware to unsuspecting users.

Prevalence in PyPI community

No prevalence information at this time

Next steps

Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.
Avoid using this software package until it is vetted as safe.

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

0 packages
found in
Top 100
2 packages
found in
Top 1k
7 packages
found in
Top 10k
1009 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.

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 their reputation by being transparent. The person behind the public-facing alias is just as important as the alias itself. Developers rarely opt to use anonymous email service accounts that hide the link between their alias and the person behind it. Software components published by anonymized developer accounts often relate to activities that are unsuited for enterprise consumption.

Prevalence in PyPI community

2 packages
found in
Top 100
10 packages
found in
Top 1k
109 packages
found in
Top 10k
17243 packages
in community

Next steps

Investigate reported detections.
You should consider delaying the software release until the investigation is completed, or until the issue is risk accepted.
Consider replacing the software component with an alternative.

Top behaviors

See all behaviors

Prevalence in PyPI community

Behavior often found in this community (Common)
75 packages
found in
Top 100
451 packages
found in
Top 1k
3488 packages
found in
Top 10k
109392 packages
in community

Prevalence in PyPI community

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

Prevalence in PyPI community

Behavior often found in this community (Common)
67 packages
found in
Top 100
520 packages
found in
Top 1k
3993 packages
found in
Top 10k
158349 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
49 packages
found in
Top 100
364 packages
found in
Top 1k
2374 packages
found in
Top 10k
87567 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
25 packages
found in
Top 100
205 packages
found in
Top 1k
1070 packages
found in
Top 10k
28156 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for narwhals

What is narwhals?

Extremely lightweight compatibility layer between dataframe libraries.

Is narwhals malicious or is it safe to use?

The Python package narwhals has been removed from registry. It was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. Malware or tampering has been detected, making it unsafe to use. The package contains risks, and the analysis results should be reviewed before it is used. Visit the Issues and Behaviors sections of the analysis for more details.

Is narwhals popular?

The Python package narwhals ranks among the top 1000 projects in this community. It has 334M recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure narwhals once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how narwhals behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a narwhals version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.