runspec-wireshark-core
Pure-Python helpers over Wireshark's tshark, capinfos and mergecap — the
logic behind runspec-wireshark. Stdlib only, no
runspec dependency, no runspec.toml, no entry points: installing it surfaces
no runnables, so a private package can import the helpers and build narrower
runnables on top.
from runspec_wireshark_core import config_from_env, summary, follow
cfg = config_from_env()
print(summary(cfg, "/var/tmp/outage.pcapng"))
print(follow(cfg, "/var/tmp/outage.pcapng", stream=3))
Every helper takes a WiresharkConfig first and returns plain data; failures
raise WiresharkError (ToolNotFoundError when tshark isn't installed).
1 maintainer
Metadata
1 maintainer
Release files for runspec-wireshark-core 0.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 | Actions |
|---|---|---|---|---|
| runspec_wireshark_core-0.1.0.tar.gz | 32.6 kB | With provenance | Details for runspec_wireshark_core-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| runspec_wireshark_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for runspec_wireshark_core-0.1.0-py3-none-any.whl |
Total release size: 61.0 kB
Release files / runspec_wireshark_core-0.1.0.tar.gz
| Download URL | runspec_wireshark_core-0.1.0.tar.gz |
|---|---|
| Size | 32.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a49f24b1bf0cb8d7f0982c4589fd76c0abcc5150f38eba1f4e8fa8256a177b4
|
|
BLAKE2b-256 checksum How to use checksums |
f682044674803a56ed5de8920d152cf3fe07a26b9733aaffbc0c1f8f7af2d00b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / runspec_wireshark_core-0.1.0-py3-none-any.whl
| Download URL | runspec_wireshark_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0085d91f39f5b70076bdf8dc94474ef092b39b7d2da14879c8a507b54e91336
|
|
BLAKE2b-256 checksum How to use checksums |
063672bb44632ad7d708b54b5360a354f15e34eef320bb34056b01f51fc0ec6b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for runspec-wireshark-core 0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for runspec_wireshark_core-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA 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.
