Easy way to use bower with your django project
1 maintainer
Metadata
1 maintainer
Release files for django-bower 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-bower-4.tar.gz | 3.6 kB | Without provenance | Details |
Release files / django-bower-4.tar.gz
| Download URL | django-bower-4.tar.gz |
|---|---|
| Size | 3.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e9f679aa76fc4fed5e03b8989a84fcae34e7cc43d25aab2eb23dde82cdc48fc
|
|
BLAKE2b-256 checksum How to use checksums |
31597d53a41ccd55998b9d8c3afa2bcc23c919b436017a46e98679cea49f7ead
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-bower 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.
