Preprocessing and Poisoning your dataset using BADCODE
1 maintainer
Metadata
1 maintainer
Release files for seedguard-beta 0.0.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 | |
|---|---|---|---|---|
| seedguard-beta-0.0.1.tar.gz | 11.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seedguard_beta-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.3 kB
Release files / seedguard-beta-0.0.1.tar.gz
| Download URL | seedguard-beta-0.0.1.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
110b39195e94bb83a3bc43d69ae1d13eb053d8178e7f9ecaaaca55ee09e942ba
|
|
BLAKE2b-256 checksum How to use checksums |
ced888767004f3cf058cd3a70bec9151f38f7b02fe497bd3b3de78ebf3600863
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / seedguard_beta-0.0.1-py3-none-any.whl
| Download URL | seedguard_beta-0.0.1-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ab71fca20b6b52c3cde8b14bdc29c9c2c7027e6cc2374809c687d68d8b9915b2
|
|
BLAKE2b-256 checksum How to use checksums |
4c7ccdae53bd424bc498ad8adb6ba5898c3498ae88e14013b3bbdde20539bdf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for seedguard-beta 0.0.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.
