Report spam calls
Jason uses this routine to report spam calls to the FTC:
` py -m jaraco.develop.report-spam-call 202-555-1212 `
It uses Splinter to automate the process of reporting a spam call through the donotcall.gov website.
It might be overly tuned to a specific class of calls, so feel free to propose extensions to the process to suit more needs.
Metadata
Release files for jaraco.home 3.10.2
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 | Actions |
|---|---|---|---|---|
| jaraco_home-3.10.2.tar.gz | 14.3 kB | Without provenance | Details for jaraco_home-3.10.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jaraco.home-3.10.2-py3-none-any.whl | Python 3 | none | any | Details for jaraco.home-3.10.2-py3-none-any.whl |
Total release size: 24.0 kB
Release files / jaraco_home-3.10.2.tar.gz
| Download URL | jaraco_home-3.10.2.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa6896366e56c00fc11364ccbf940f4c42248f59ca7a88750df145afd540d66f
|
|
BLAKE2b-256 checksum How to use checksums |
b6f62ed9b383164183f523869ad93d9173a000591a0ffa9c3da7c3b426d32d51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Release files / jaraco.home-3.10.2-py3-none-any.whl
| Download URL | jaraco.home-3.10.2-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ed3ecf4247d93b6246c3a0ac7d2e2fe57d79835020609a907ad37e26ec3fbed5
|
|
BLAKE2b-256 checksum How to use checksums |
aaa66c2406157e60569e496b9d6d119f6a700c46af36fab898e75c2c67c8acf7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.4
|
Security for jaraco.home 3.10.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.