Metadata
1 maintainer
Release files for django-nordigen 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 | |
|---|---|---|---|---|
| django_nordigen-0.1.0.tar.gz | 7.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_nordigen-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.1 kB
Release files / django_nordigen-0.1.0.tar.gz
| Download URL | django_nordigen-0.1.0.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91e8e11c116199d3c133f51f3cd5ce23f179785b2c4b04f6a769be6516a8a2ff
|
|
BLAKE2b-256 checksum How to use checksums |
df1447cef80df37843f049db20cb4dad127003e2d0329b29bfd603986ffb77f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.10.10 Darwin/22.3.0
|
Release files / django_nordigen-0.1.0-py3-none-any.whl
| Download URL | django_nordigen-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ad6bb0c657f562521e1ad2a39b92fecee427fcad922d11dcc1120d429be277e
|
|
BLAKE2b-256 checksum How to use checksums |
42c1f0cee151655d21435ae58dec0f1ff1e7757f5b8e2bc23cb0c6137ef459a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.4.0 CPython/3.10.10 Darwin/22.3.0
|
Security for django-nordigen 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.
