Win_purge
It is a very bad idea to run Python code from the internet that modifies the Windows Registry. Minor bugs in Win_purge can be critical - any could inadvertantly cripple your system. Win_purge can delete important registry keys if you let it - I do not know the purpose of every Registry key, and there is no special treatment of any Windows edition or setups (the code can quickly become out of date - the frequency of automatic Windows updates in the modern age, means Win_purge could have become inadvertantly unsafe at any point in time).
I draw your attention to the last paragraph of the MIT license:
"THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
That said, if you accept the risk, then win_purge has been designed to take the following steps to protect your system, based on a simple text search:
-
Refuses to run if a matching registered uninstaller is found (as this should be run instead).
-
Uses exactly the same search code for a safe dry run, as for a run that deletes matching keys - no surprising results.
-
Requires a special force switch on the CLI to delete and modify keys.
-
Prompts for confirmation, skip or quit (y/n/quit respectively) before each change.
-
Tries to identify system path keys. In recognised path keys, win_purge modifies the path name/data in the value instead (removing matching paths from the system wide path and from the user's path).
-
Backs up each key before modification or deletion (with
reg export), and consolidates the backups after each session. -
Uses send2trash to send the temporary key back up files to the Recycle Bin (does not permanently delete them).
-
Win_purge can also delete matching application files from common installation directories.
Metadata
Release files for win-purge 0.0.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 |
|---|---|---|---|---|
| win_purge-0.0.2.tar.gz | 11.5 kB | Without provenance | Details for win_purge-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| win_purge-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for win_purge-0.0.2-py3-none-any.whl |
Total release size: 25.8 kB
Release files / win_purge-0.0.2.tar.gz
| Download URL | win_purge-0.0.2.tar.gz |
|---|---|
| Size | 11.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
753a94cd6fbc7b01ca7f7499bed4cc7687a65b8e4e0dadc8425d93989d1643cf
|
|
BLAKE2b-256 checksum How to use checksums |
0a30ea45a655a925384e016cd8712d4031caa62bf59243839e6617ba341ea28a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.4.20
|
Release files / win_purge-0.0.2-py3-none-any.whl
| Download URL | win_purge-0.0.2-py3-none-any.whl |
|---|---|
| Size | 14.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
daf8e8e4d1724071c847fb876cc01658385e76824e5900ebdfd656090ea26ed9
|
|
BLAKE2b-256 checksum How to use checksums |
90a37c14db9df96a5e641f12cae22c474bc7c79a9f2453e8def6b1e0f2b8a231
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.4.20
|
Security for win-purge 0.0.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.