<|start_of_focus|># wlkngkr
wlkngkr is a modular, extensible environment probing framework. Each probe is a focused Python class, the runner orchestrates them, and the CLI produces structured pydantic reports that you can feed into logging, diagnostics, or compliance tooling.
Features
- Batteries-included probes for system and user context.
- Central registry + runner that selects probes by name or tag.
- Typed results (
EnvReport,ProbeResult) built withpydantic. - Typer-powered CLI that doubles as a Python API (
ProbeRunner). - Shipping via Apache 2.0 so it can live inside automation pipelines.
Installation
Stable releases will be published to PyPI.
pip install wlkngkr
# or, with uv (recommended for contributors)
uv tool install wlkngkr
If you want to work from the repo:
git clone https://github.com/cprima-forge/cpmf-uiprc-diag.git
cd cpmf-uiprc-diag
uv sync --dev
Usage
List available probes and run everything (default JSON output):
uv run wlkngkr --list
uv run wlkngkr --probe system --probe user
Prefer human-friendly status lines? Use the built-in text formatter:
uv run wlkngkr --format text
[system] status=success
[user] status=success
Python API usage is equally straightforward:
from wlkngkr.runner import ProbeRunner
from wlkngkr.config import RunnerConfig
runner = ProbeRunner()
report = runner.run(RunnerConfig(tags=["core"]))
print(report.model_dump())
Development
uv sync --all-extras --dev
uv run pytest
Useful scripts:
uv run wlkngkr run --probe system– run a single probeuv run wlkngkr --list– check registry state
Releasing
- Update
CHANGELOG.mdand bumppyproject.toml's version. - Commit the release (
git commit -am "chore: release v0.x.y"). - Tag it (
git tag v0.x.y && git push origin v0.x.y). - GitHub Actions (
.github/workflows/release.yml) will run tests, build the distribution viauv build, and publish to PyPI. When aPYPI_API_TOKENsecret is present, the workflow uploads withtwine>=6.1.0; otherwise it falls back to PyPI Trusted Publishing (OIDC).
License
Apache License 2.0 – see LICENSE.
Maintainer
Christian Prior-Mamulyan (@cprima) — cprior@gmail.com<|end_of_focus|>
Metadata
Release files for wlkngkr 0.1.2
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 | |
|---|---|---|---|---|
| wlkngkr-0.1.2.tar.gz | 18.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wlkngkr-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.3 kB
Release files / wlkngkr-0.1.2.tar.gz
| Download URL | wlkngkr-0.1.2.tar.gz |
|---|---|
| Size | 18.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c0dfb3efc60b3da3b1a7f8b8249f7913a9631cd65b474fcfda7fc3e2a68153a3
|
|
BLAKE2b-256 checksum How to use checksums |
44222b839b1a02e9bda38fb1a54c8af807f3bd537a8651885c783eb92c626795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / wlkngkr-0.1.2-py3-none-any.whl
| Download URL | wlkngkr-0.1.2-py3-none-any.whl |
|---|---|
| Size | 26.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d46c3620d00a48c7e2a464b75b89e49f7bff4dc28cce49ceff4cdec378d6cfc0
|
|
BLAKE2b-256 checksum How to use checksums |
34e5e72b0ca0ffd42f055a3076182d805193a2be2b65720b7652a9fe7777e425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for wlkngkr 0.1.2
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.