Long Description: Poisoning Functionalities for your dataset
1 maintainer
Metadata
1 maintainer
Release files for seedpoisoner 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 | |
|---|---|---|---|---|
| seedpoisoner-0.0.1.tar.gz | 8.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seedpoisoner-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / seedpoisoner-0.0.1.tar.gz
| Download URL | seedpoisoner-0.0.1.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94fc5f9f8dd729559acbcc52f454b9e256d2bf86f976ea5d6dafbd964b02485c
|
|
BLAKE2b-256 checksum How to use checksums |
a4e4c616dde3340a2df734457871e660023855ee020168214107ecbf0dcc979b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Release files / seedpoisoner-0.0.1-py3-none-any.whl
| Download URL | seedpoisoner-0.0.1-py3-none-any.whl |
|---|---|
| Size | 8.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cbb4ee9a0edf3481ca6af675d9bf4ff49bc3788b23dfa2820335d2ac44940160
|
|
BLAKE2b-256 checksum How to use checksums |
6522805aeb931dbf35186c8b175871f917af7e5d570df24a991a688c0bf6cf19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.11.6
|
Security for seedpoisoner 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.
