The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for drf-base 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 | |
|---|---|---|---|---|
| drf_base-0.1.0.tar.gz | 5.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| drf_base-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / drf_base-0.1.0.tar.gz
| Download URL | drf_base-0.1.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c891462e9a93a485d5f5bec680ac896f48cdf4c8fedcc8f8761b31217cc9e43c
|
|
BLAKE2b-256 checksum How to use checksums |
f130fb8a90744431f13b9932ac69eee733ed88f79466852bd9aab0996dfb4174
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Release files / drf_base-0.1.0-py3-none-any.whl
| Download URL | drf_base-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a34791846a148486c666bc7266176eda94563f077012a0a17795cae50f2499c
|
|
BLAKE2b-256 checksum How to use checksums |
aa90dfa094fe6ac6bafc2905bbf0225903966a511f94c26cb254aa2404263c24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.11
|
Security for drf-base 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.
