The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for squid-crm 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 | |
|---|---|---|---|---|
| squid_crm-0.1.0.tar.gz | 2.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| squid_crm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.3 kB
Release files / squid_crm-0.1.0.tar.gz
| Download URL | squid_crm-0.1.0.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1fab17db440b4534e273d8d479cb12e96b6b92837792e70c934eade3713e5b92
|
|
BLAKE2b-256 checksum How to use checksums |
846894252e559dc3a5f8db65414aa310f5df0fba3d54384f6019e860fe5b2225
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / squid_crm-0.1.0-py3-none-any.whl
| Download URL | squid_crm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 2.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4c1dadd3537b4b8145db8ebca68468ded510c3318daa84142048e10a4dda1cf
|
|
BLAKE2b-256 checksum How to use checksums |
7924a20afd24a14b33f963e90f61318fbcaf59726a01946bff18da90613ab430
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for squid-crm 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.
