1 maintainer
Metadata
1 maintainer
Release files for asm-opcode-analyzer 1.1.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 | |
|---|---|---|---|---|
| asm-opcode-analyzer-1.1.0.tar.gz | 13.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asm_opcode_analyzer-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.5 kB
Release files / asm-opcode-analyzer-1.1.0.tar.gz
| Download URL | asm-opcode-analyzer-1.1.0.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ba9dbd369534dae0e4f59f7560fcbed1ce6eb9ed683eaf52aa16f6cc0ff7972
|
|
BLAKE2b-256 checksum How to use checksums |
05fc033aacde8ac52b51e1e3c754dbda75302c2e84a6ac152ec59e4759d3b105
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Release files / asm_opcode_analyzer-1.1.0-py3-none-any.whl
| Download URL | asm_opcode_analyzer-1.1.0-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c27dae45239d231e85c33223812622c1f54977a5a2fc35a7189898c2d92dda40
|
|
BLAKE2b-256 checksum How to use checksums |
08d9c3cc3aa196cbad9f0c343b76bd2cda15e0ae55eb5134008bca94247b24e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.17
|
Security for asm-opcode-analyzer 1.1.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.
