Skip to main content

Rephrase Hyperforge agents

Metadata

Release files for hyperforge-restart 1.0.0.post74

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

Built distribution (wheel)

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

Total release size: 8.7 kB

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

Download URL hyperforge_restart-1.0.0.post74.tar.gz
Size 4.7 kB
Tags Source
SHA-256 checksum
How to use checksums
9e879470939bc2498ba602f323363bd9b80976f7a08f216a9f0564cb378119e5
BLAKE2b-256 checksum
How to use checksums
4d7ce2243f011a603040f1fd250bf734a22c1df21d92b157278eabfd671839f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 23, 2026.

Transparency log

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

Download URL hyperforge_restart-1.0.0.post74-py3-none-any.whl
Size 4.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d4c38576e820b733d0b3128ab1fc6008ea8ac314f56bbcade085f14bf680fd19
BLAKE2b-256 checksum
How to use checksums
8e35823d659b000fde6b798aa9fa348159aa5f87de2f6240a9a146a0d8f6dcf8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 23, 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