The author of this package has not provided a project description
Metadata
Release files for browserchief 0.1.0
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 | |
|---|---|---|---|---|
| browserchief-0.1.0.tar.gz | 1.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| browserchief-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 kB
Release files / browserchief-0.1.0.tar.gz
| Download URL | browserchief-0.1.0.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf1d7b652cf4629bfdae06b962bad2360038fcca58c2dbc6d2ab6d6a8709c64e
|
|
BLAKE2b-256 checksum How to use checksums |
5ab43ea8439f069919532eed1c4743f7ae01108ddda95da0919a99835fd77e84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / browserchief-0.1.0-py3-none-any.whl
| Download URL | browserchief-0.1.0-py3-none-any.whl |
|---|---|
| Size | 1.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
371340b0dc29f4c1febfc9ff96c8826721370dff2d4673859994349fd6f5229a
|
|
BLAKE2b-256 checksum How to use checksums |
d802151e5e468f24742cdf09e5f59eefda60b9ed4122edcd59895ebe527f6416
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for browserchief 0.1.0
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.