PyPI PACKAGE

esptool 5.5.0

Warn

PkgFire would install this release with a warning.·Checked 2 hours ago·Published 8 October 2026

pypi.org

Why

  • warnSuspicious behaviour

    Dependency mismatch between PyPI metadata and pyproject.toml: In pyproject.toml but NOT in PyPI metadata: bitstring In PyPI metadata but NOT in pyproject.toml: coverage~, czespressif, esp-docs, pre-commit, pyelftools, pytest, pytest-rerunfailures, python-pkcs11, requests, sphinx-tabs

Provenance

A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.

Signature
Not signed
Build provenance
Attested

Licence and upkeep

Licence
non-standard
Source
github.com/espressif/esptool ↗
OpenSSF Scorecard
3.3 / 10

What the code does

On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.

Code reading

PkgFire's own reading of the files: what the code can do.

  • code-evalespefuse/efuse/mem_definition_base.py, esptool/loader.py
  • code-networkesp_rfc2217_server/__init__.py
  • import-networkesp_rfc2217_server/__init__.py

Source patterns

Patterns found in the source, including those malware is known to use.

  • capability-filesystem-read
  • capability-network-outbound
  • capability-process-schedule
  • capability-process-spawn
  • metadata_mismatch

Other checked releases

Check every dependency before it installs

This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.

Start free How it works