The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for asyngram 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 | |
|---|---|---|---|---|
| asyngram-0.1.2.tar.gz | 36.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| asyngram-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 82.4 kB
Release files / asyngram-0.1.2.tar.gz
| Download URL | asyngram-0.1.2.tar.gz |
|---|---|
| Size | 36.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ce39f789fcaa4a5d4284c9f7682e2786ebe54ee75e8f07eda77ceac205534f9
|
|
BLAKE2b-256 checksum How to use checksums |
4e498261feae1cb20b97bc98e7aa614dd268cd503685c15255adfe5b0d252802
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.4
|
Release files / asyngram-0.1.2-py3-none-any.whl
| Download URL | asyngram-0.1.2-py3-none-any.whl |
|---|---|
| Size | 46.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
977b97c3ab5a4a1869bc2ee9878edc24422db6f9f85e71ee742b6bad42b9d16a
|
|
BLAKE2b-256 checksum How to use checksums |
47c6ba5ffa5a7044b8beecd87cd2e41dcb52606371ddce766dbc634361d5d1bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.4
|
Security for asyngram 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.
