Downloadable Tools

Downloadable tooling is reserved for future packages that cannot reasonably run as browser-only utilities. This section is intentionally empty until a tool has a release owner, version, platform target, checksum, signature, release notes, and support boundary.

The absence of binaries is deliberate. A security lab should not publish executable artifacts casually. When PCL hosts its first downloadable tool, the release page should make verification routine: filename, version, SHA-256, signing key, build provenance, platform support, expected permissions, and known limitations should be visible before the download link.

Release Requirements

A downloadable tool release must include:

• stable tool identifier and semantic version;
• supported operating systems and architectures;
• SHA-256 digest and signing material;
• release notes and changelog;
• license and support boundary;
• expected network behavior;
• telemetry/storage statement;
• uninstall or cleanup notes when applicable.

Downloadable tooling will appear here after the release process supports checksums, signatures, version notes, platform targets, and a support boundary. Until then, the public tool surface remains browser-local so users can inspect and run utilities without installing binaries from this site.

Current Status

No downloadable tools are published at this time. Browser tools remain the active public tooling surface.

A current-status section should be explicit even when there is nothing to publish. Empty states are acceptable when they tell users what is intentionally absent and where to look next.