Skip to main content

Rephrase Hyperforge agents

Metadata

Release files for hyperforge-rephrase 1.0.0.post83

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hyperforge-rephrase 1.0.0.post83
File Size Uploaded
hyperforge_rephrase-1.0.0.post83.tar.gz 7.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for hyperforge-rephrase 1.0.0.post83
File Interpreter ABI Platform
hyperforge_rephrase-1.0.0.post83-py3-none-any.whl Python 3 none any Details

Total release size: 13.5 kB

Release files / hyperforge_rephrase-1.0.0.post83.tar.gz

Download URL hyperforge_rephrase-1.0.0.post83.tar.gz
Size 7.2 kB
Tags Source
SHA-256 checksum
How to use checksums
30bc17c5f2d5e063b436b58fe0ac2bee034eac3f7136765b99731f58435ddbfa
BLAKE2b-256 checksum
How to use checksums
9c2a5713f48fb15cafd737a7be3a2ed3c9a986b71c596f08638d0244c984e01c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

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 Sep 10, 2026.

Transparency log

Release files / hyperforge_rephrase-1.0.0.post83-py3-none-any.whl

Download URL hyperforge_rephrase-1.0.0.post83-py3-none-any.whl
Size 6.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
45cf541b04d8b55f40f5dc654d075bb64de1b8270b2d1348fb6ea6b63141929f
BLAKE2b-256 checksum
How to use checksums
7b1da8fe880412d57cd870f72d170b05f0a01e4fa7c5012795d27fc367b2a56e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

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 Sep 10, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page