The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for snapforge 0.1.2
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 | |
|---|---|---|---|---|
| snapforge-0.1.2.tar.gz | 2.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| snapforge-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.5 kB
Release files / snapforge-0.1.2.tar.gz
| Download URL | snapforge-0.1.2.tar.gz |
|---|---|
| Size | 2.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
849a98813e280c261734fdd72bc8443aed7331c3fff9fdc59d0d346b13c03bf8
|
|
BLAKE2b-256 checksum How to use checksums |
f7529ffc25aa64431dedaca9072d793722db2f88e9223b52feee394d36426501
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / snapforge-0.1.2-py3-none-any.whl
| Download URL | snapforge-0.1.2-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
695c4ab5bb781889d3bd16dda4a40c8582e15a54cb200e7bbb9ec21ef9a5800d
|
|
BLAKE2b-256 checksum How to use checksums |
b1c4fbeba26e0563f3a7f3a528f2d60dc784dbdf3b9643cf14893021887571cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for snapforge 0.1.2
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.
