The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for squid-crm 0.2.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.2.0.tar.gz | 4.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| squid_crm-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.6 kB
Release files / squid_crm-0.2.0.tar.gz
| Download URL | squid_crm-0.2.0.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a786bab7305076e4b236315b3b5a51ed0ad0fa6b9a576a3afec0c581ea22e26d
|
|
BLAKE2b-256 checksum How to use checksums |
6faedab0afd7094922623ff56163cd80a71023e2add0efd076c56f5cee3c0d4a
|
| 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.2.0-py3-none-any.whl
| Download URL | squid_crm-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a8fb712696c4f0c44b6db61d015fb25ef5db812f11713d733c5a06951254257
|
|
BLAKE2b-256 checksum How to use checksums |
36e64c9607629212cfe877317c1bb3764b89520873f6692eefbe7e55e1d7c2d9
|
| 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.2.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.
