The author of this package has not provided a project description
Metadata
Release files for aiforge-framework 0.3.0
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 | |
|---|---|---|---|---|
| aiforge_framework-0.3.0.tar.gz | 22.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiforge_framework-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.9 kB
Release files / aiforge_framework-0.3.0.tar.gz
| Download URL | aiforge_framework-0.3.0.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e719f86fb178e8cd9f40b0b4b3e1c83071270407b5bf665c5fc48d6ed6040fb8
|
|
BLAKE2b-256 checksum How to use checksums |
5662ee2a2e5cb4d445935280571a05a621d9fa1ce45a3b9596cc7b72aeb5e619
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.9
|
Release files / aiforge_framework-0.3.0-py3-none-any.whl
| Download URL | aiforge_framework-0.3.0-py3-none-any.whl |
|---|---|
| Size | 28.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c58b46519502a476dca25f8755f35f643e7dcd9f97ba0a7d94e9235ff5d4517
|
|
BLAKE2b-256 checksum How to use checksums |
1041fdc5eba27693f11df9d49dd2785f1b61c4dd0c93212cc186558f78a45bc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.9
|
Security for aiforge-framework 0.3.0
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.