Skip to main content

Rephrase Hyperforge agents

Metadata

Release files for hyperforge-restart 1.0.0.post73

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-restart 1.0.0.post73
File Size Uploaded
hyperforge_restart-1.0.0.post73.tar.gz 4.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for hyperforge-restart 1.0.0.post73
File Interpreter ABI Platform
hyperforge_restart-1.0.0.post73-py3-none-any.whl Python 3 none any Details

Total release size: 8.7 kB

Release files / hyperforge_restart-1.0.0.post73.tar.gz

Download URL hyperforge_restart-1.0.0.post73.tar.gz
Size 4.7 kB
Tags Source
SHA-256 checksum
How to use checksums
7c27df1995c3cdbe39924512d286da16ae49e53e563eae736c3b806537f628f2
BLAKE2b-256 checksum
How to use checksums
1be4c46039f2d7840cb267c45d038781446599e1264134cf2bb1d02265d404ff
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 11, 2026.

Transparency log

Release files / hyperforge_restart-1.0.0.post73-py3-none-any.whl

Download URL hyperforge_restart-1.0.0.post73-py3-none-any.whl
Size 4.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d3d6bd2f83e2f44544f123f25abcaab10c3049406c44ba7f9beddf795e42bcdf
BLAKE2b-256 checksum
How to use checksums
ffa08c87e27e8b24de17e5dd36c5d2fa6f9d738158ead00f5ab0ebdec8f6c24f
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 11, 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