Site and organization multi-tenancy management for Appsembler Tahoe
1 maintainer
Metadata
1 maintainer
Release files for tahoe-sites 1.3.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 | |
|---|---|---|---|---|
| tahoe-sites-1.3.2.tar.gz | 18.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tahoe_sites-1.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.7 kB
Release files / tahoe-sites-1.3.2.tar.gz
| Download URL | tahoe-sites-1.3.2.tar.gz |
|---|---|
| Size | 18.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aaa0f48f5703f254b481329fed1c2c9a6f7d23ff7113dd89bde5d6f8108c31f2
|
|
BLAKE2b-256 checksum How to use checksums |
4536a52494432968ad0fd59429054095320e0b112ef5bb9ce1dc71c74f23fc69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Release files / tahoe_sites-1.3.2-py3-none-any.whl
| Download URL | tahoe_sites-1.3.2-py3-none-any.whl |
|---|---|
| Size | 25.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4e8f439398e147ffbdca7277d059a9240445fbfe4e4e804d44aa49babe77910
|
|
BLAKE2b-256 checksum How to use checksums |
171c7835236fbf1809e505677f4ef897e297a0a43e62f6741cd2842a24ffd16f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.14
|
Security for tahoe-sites 1.3.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.
