The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for bibtex-clean 0.0.5
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 | |
|---|---|---|---|---|
| bibtex_clean-0.0.5.tar.gz | 21.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bibtex_clean-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 48.9 kB
Release files / bibtex_clean-0.0.5.tar.gz
| Download URL | bibtex_clean-0.0.5.tar.gz |
|---|---|
| Size | 21.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ccb2b3b7bb415cf17043a44591f37e9d629c506944605d5856bc777aeb196e54
|
|
BLAKE2b-256 checksum How to use checksums |
7e75c85586542ff210b59d7e8a3451ed9c0c9af3644d81867d43aa46a413dd14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Release files / bibtex_clean-0.0.5-py3-none-any.whl
| Download URL | bibtex_clean-0.0.5-py3-none-any.whl |
|---|---|
| Size | 27.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d662b33ef36bcd25cc5fb210ee0c35b95c997430edc0e8df13e72ca8bceb270
|
|
BLAKE2b-256 checksum How to use checksums |
68282c62dee3e803d8077f68f6b6f2e947502268ee0c04ed7eca41e406371b70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.10
|
Security for bibtex-clean 0.0.5
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.
