The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for Arjun-STT 0.1.2
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 | |
|---|---|---|---|---|
| arjun_stt-0.1.2.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arjun_stt-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.4 kB
Release files / arjun_stt-0.1.2.tar.gz
| Download URL | arjun_stt-0.1.2.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0da49a65691d4b4733cd219914f16d4603c2b080f93944c79a632932bf9154b0
|
|
BLAKE2b-256 checksum How to use checksums |
d9c18155be2f85bd97dde9096cddd2e478a1ba0b7f93fa81af32edfa10731487
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Release files / arjun_stt-0.1.2-py3-none-any.whl
| Download URL | arjun_stt-0.1.2-py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d69eeac67222f76f54c470a0cf1802a31c5c3116b157ad75c85f22496d1b48ad
|
|
BLAKE2b-256 checksum How to use checksums |
29ed6121d396dba150fbff185aec369581b5ee893561acfc02c209a0ddfb5c92
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.2
|
Security for Arjun-STT 0.1.2
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.
