The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for django-filepond 0.1.4
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_filepond-0.1.4.tar.gz | 30.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_filepond-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.7 kB
Release files / django_filepond-0.1.4.tar.gz
| Download URL | django_filepond-0.1.4.tar.gz |
|---|---|
| Size | 30.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
02fdbe44637a489364e141ad4478a7dcc9d5f41ab3fb76388ae661e63c8a1958
|
|
BLAKE2b-256 checksum How to use checksums |
b008da4a4b0c28282e3bf00059c98d4b8ca6ac1c9400e84f9a26ec8b93340868
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.31.0
|
Release files / django_filepond-0.1.4-py3-none-any.whl
| Download URL | django_filepond-0.1.4-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
35929548191b1cc6ca6fb5959b0b5e90481bb4bebddc656d46586001390de223
|
|
BLAKE2b-256 checksum How to use checksums |
96f015b28cd20f902815789e745fedac2a3a27032b239f0305222b6200c9c65c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.31.0
|
Security for django-filepond 0.1.4
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.
