The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for pymetaphone-br 0.0.3
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 | |
|---|---|---|---|---|
| pymetaphone_br-0.0.3.tar.gz | 11.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pymetaphone_br-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.9 kB
Release files / pymetaphone_br-0.0.3.tar.gz
| Download URL | pymetaphone_br-0.0.3.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45dfa2d01e52865ce5e5440293a5ad3a0d77a24c0b2f081935ae423831e19ead
|
|
BLAKE2b-256 checksum How to use checksums |
250979666ccb830b447484a06324da67be78a2a51b544b25e58e9d2b4ecb0525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Release files / pymetaphone_br-0.0.3-py3-none-any.whl
| Download URL | pymetaphone_br-0.0.3-py3-none-any.whl |
|---|---|
| Size | 12.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dac81a9ad4df4d34fa214aba849543ee97f3b9ad19c627c9ffdbe3946228338b
|
|
BLAKE2b-256 checksum How to use checksums |
5e9c5991de07cf58a921e7433afb6a062c688ff438af75a145817207827234a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.9
|
Security for pymetaphone-br 0.0.3
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.
