manifests
Initial PyPI package scaffold for manifests, using uv for build and publish.
Local workflow
uv build
uv publish
uv publish reads UV_PUBLISH_TOKEN automatically.
If your token is stored as PYPI_TOKEN, run:
export UV_PUBLISH_TOKEN="$PYPI_TOKEN"
uv publish
TestPyPI
uv publish --publish-url https://test.pypi.org/legacy/
1 maintainer
Metadata
1 maintainer
Release files for manifests 0.1.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 | Actions |
|---|---|---|---|---|
| manifests-0.1.0.tar.gz | 765 Bytes | Without provenance | Details for manifests-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| manifests-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for manifests-0.1.0-py3-none-any.whl |
Total release size: 2.4 kB
Release files / manifests-0.1.0.tar.gz
| Download URL | manifests-0.1.0.tar.gz |
|---|---|
| Size | 765 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
01a95edcb2ac22f5d2a97fdb892792bb926a48487ff5c479002e2eea99e47d13
|
|
BLAKE2b-256 checksum How to use checksums |
e2ca6dc0be699525d9a4e912e7f3d2a533fd8acdf1c21f2fd7a9890d466db76a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.14 {"installer":{"name":"uv","version":"0.9.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / manifests-0.1.0-py3-none-any.whl
| Download URL | manifests-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c13d829e906daf31ef950b5145662a02e2b8adb8da9ef51df3a9c08dd4e75e1a
|
|
BLAKE2b-256 checksum How to use checksums |
9d10f10d017dfdb1d67b7677447233071457d9e9cc1d1b3e72a8b0cdaa1f1adf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.14 {"installer":{"name":"uv","version":"0.9.14","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for manifests 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
