# CHANGELOG
## Version 0.1.9 (July 12th, 2017) * Implemented proxy packages reception.
## Version 0.1.8 (July 6th, 2017) * New preloaded ports from args (eg. -l 3123,9123).
## Version 0.1.6 (July 6th, 2017) * Line breaks are highlighted in packaged received. * Admin error are propagated to every report client. * New flag for the client test, which indicates that a break line will be added after the payload. (–br).
## Version 0.1.5 (June 23th 2017) * New built and standallone sender client. (python -m sokery.client) * Dark interface. * Nicer coloring for texts. * Added origin to packages received.
## Version 0.1.3 (June 12th 2017) * New option for echoing everything received.
## Version 0.1.3 * Added response messages for errors and success port opening.
## Version 0.1.2 * Autoimplemented module, running in port 4991. * Fixed index.html access.
Metadata
Release files for sokery 0.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 |
|---|---|---|---|---|
| sokery-0.2.0.tar.gz | 66.5 kB | Without provenance | Details for sokery-0.2.0.tar.gz |
Release files / sokery-0.2.0.tar.gz
| Download URL | sokery-0.2.0.tar.gz |
|---|---|
| Size | 66.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60e76aad5d61ae9a7c2bd0f485fb2fa80ec68b0d6dea86a3bd915b9485d478b4
|
|
BLAKE2b-256 checksum How to use checksums |
5cea783edd45c6216dbcace670b46a6f204333138970a89b9ed738ead2cc7b3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sokery 0.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.