The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for jsomark 0.2.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 | |
|---|---|---|---|---|
| jsomark-0.2.0.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jsomark-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.1 kB
Release files / jsomark-0.2.0.tar.gz
| Download URL | jsomark-0.2.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf0d111ebdc59f0dca48ee6c5c67883ca4535d15291867a86287d3a7e585e668
|
|
BLAKE2b-256 checksum How to use checksums |
a5061139ba310b6acc96a5f362a485ae0922a8767d0061380bbefb19d7c5d883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.6.9 Linux/4.15.0-88-generic
|
Release files / jsomark-0.2.0-py3-none-any.whl
| Download URL | jsomark-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de8a8dfa9ae3f02963055b3b61d7dedd4e60d65ef56c5900be9d3a020125e314
|
|
BLAKE2b-256 checksum How to use checksums |
683b24797ac01758301381857ef412ccbbd84ba895e60fc2ae95a9a6758284d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.0.5 CPython/3.6.9 Linux/4.15.0-88-generic
|
Security for jsomark 0.2.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.
