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

hyperloglog

Artifact:
latest
Top 10k
HyperLogLog cardinality counter
License: Copyleft (LGPL-2.1-or-later)
Published: 3 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
No evidence of software tampering
Malware
No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

Popularity

2.91M
Total Downloads
1
Contributor
2
Declared Dependencies
7
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. Some open source repositories allow the developers to take down software component versions that they have published. For open source projects, version unpublishing is uncommon. Versions are typically removed due to a security incident, such as malicious code tampering or accidental development secrets exposure. Software developers often prioritize taking down such packages before informing the community that they have experienced a security incident. Therefore, it is prudent to review the reasons behind software version removals as these events might be a signal of an ongoing software supply chain attack.

Prevalence in PyPI community

No prevalence information at this time

Next steps

Review software component documentation for the reasons behind the recent version removal.
If the software version was removed due to a security incident, 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.

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 often found in this community (Common)
75 packages
found in
Top 100
593 packages
found in
Top 1k
4478 packages
found in
Top 10k
229841 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
59 packages
found in
Top 100
362 packages
found in
Top 1k
2383 packages
found in
Top 10k
79893 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
71 packages
found in
Top 100
502 packages
found in
Top 1k
4036 packages
found in
Top 10k
214507 packages
in community

Prevalence in PyPI community

Behavior often found in this community (Common)
97 packages
found in
Top 100
816 packages
found in
Top 1k
6970 packages
found in
Top 10k
463877 packages
in community

Top vulnerabilities

No vulnerabilities found.

FAQ for hyperloglog

What is hyperloglog?

HyperLogLog cardinality counter. For more information about this package, visit its homepage.

Is hyperloglog malicious or is it safe to use?

The Python package hyperloglog was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is hyperloglog popular?

The Python package hyperloglog ranks among the top 10000 projects in this community. It has 3M 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 hyperloglog once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how hyperloglog behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a hyperloglog 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.