Savanna project
Savanna at wiki.openstack.org: https://wiki.openstack.org/wiki/Savanna
Launchpad project: https://launchpad.net/savanna
Savanna docs site: https://savanna.readthedocs.org/en/latest/index.html
Roadmap: https://wiki.openstack.org/wiki/Savanna/Roadmap
Quickstart guide: https://savanna.readthedocs.org/en/latest/devref/quickstart.html
How to participate: https://savanna.readthedocs.org/en/latest/devref/how_to_participate.html
License
Copyright (c) 2013 Mirantis Inc.
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0
1 maintainer
Metadata
1 maintainer
Release files for savanna 0.2.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 | |
|---|---|---|---|---|
| savanna-0.2.2.tar.gz | 521.9 kB | Without provenance | Details |
Release files / savanna-0.2.2.tar.gz
| Download URL | savanna-0.2.2.tar.gz |
|---|---|
| Size | 521.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79c7e8e818b949314712d0ac2524b4381a87c9feb79e0f6822883481e7e3870d
|
|
BLAKE2b-256 checksum How to use checksums |
26cc80781cd9e253fe04b455b51e36e1b630c47ea999b2494fd3f2de005a6949
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for savanna 0.2.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
