The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for squid-crm 0.2.1
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.1.tar.gz | 6.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| squid_crm-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.7 kB
Release files / squid_crm-0.2.1.tar.gz
| Download URL | squid_crm-0.2.1.tar.gz |
|---|---|
| Size | 6.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d03b89a2b405f1b9dc4da5f0b6970e94173fe53da051e421d07af81e99be8b3
|
|
BLAKE2b-256 checksum How to use checksums |
4203321b0179e5917105f6fe63f4a6feee3cea1f89378e7fb412d8ea5db93535
|
| 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.1-py3-none-any.whl
| Download URL | squid_crm-0.2.1-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3eeecc4c52d38ab77fe1b5309a5b83d2f24b39f4ba034b546bbbdb9a074de2b0
|
|
BLAKE2b-256 checksum How to use checksums |
2668e5305a5e3fcfc059a9f5b1859e09a627ed4a2437811bf822374a65864e8f
|
| 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.1
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.
