esp-cryptoauth-utility
The python utility helps to configure and provision ATECC608 chip connected to an ESP module. Currently the utility is supported for ESP32, ESP32-S3, ESP32-C2, ESP32-C3, ESP32-C5, ESP32-C6, ESP32-C61, ESP32-H2 and ESP32-P4.
The esp-cryptoauth-utility is hosted on github.
Documentation
Visit online esp-cryptoauth-utility documentation or run secure_cert_mfg.py -h.
License
The License for the project can be found here
Metadata
Release files for esp-cryptoauth-utility 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| esp_cryptoauth_utility-1.2.0.tar.gz | 1.5 MB | Without provenance | Details for esp_cryptoauth_utility-1.2.0.tar.gz |
Release files / esp_cryptoauth_utility-1.2.0.tar.gz
| Download URL | esp_cryptoauth_utility-1.2.0.tar.gz |
|---|---|
| Size | 1.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cfd603e8e45b74b5360ac0bb37973bafad4f0a771ca9f331503cc8a3f502ac1c
|
|
BLAKE2b-256 checksum How to use checksums |
3dddf0a544785c80c0bb34ff43a0a1441691262858cf5a169a2584be3e72bb55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for esp-cryptoauth-utility 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.