The author of this package has not provided a project description
1 maintainer
Metadata
1 maintainer
Release files for inscodeai 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 | |
|---|---|---|---|---|
| inscodeai-0.2.0.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| inscodeai-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.0 kB
Release files / inscodeai-0.2.0.tar.gz
| Download URL | inscodeai-0.2.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8cbbcbaa0d65a57c6b6e39cbe872ad59d14809b0175acd93663df8327317a828
|
|
BLAKE2b-256 checksum How to use checksums |
5e2030f66d671dae75c4c05d53546bbace4ad9141a92583c0ec1893acb7698cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Release files / inscodeai-0.2.0-py3-none-any.whl
| Download URL | inscodeai-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d72b1b131ccb072523ebb0fdc6afd4d46bd879241cbaaa50d5c46577222d867
|
|
BLAKE2b-256 checksum How to use checksums |
ca808790ca935d1cc372723a99c8e74d72e51de7d7a928da7e05f84a3815e132
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.16
|
Security for inscodeai 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.
