1 maintainer
Metadata
1 maintainer
Release files for langchain-guidelines 0.0.1
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 | |
|---|---|---|---|---|
| langchain_guidelines-0.0.1.tar.gz | 7.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langchain_guidelines-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.3 kB
Release files / langchain_guidelines-0.0.1.tar.gz
| Download URL | langchain_guidelines-0.0.1.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
060b4c0d790832bdcf380237f9617a245f7c00ec7e4fa14bfdd8196a3a85133f
|
|
BLAKE2b-256 checksum How to use checksums |
c5510ffdb5e9c93af36947fef4e096cce5c8b48fed4918563966d8a4a3d1b30d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Release files / langchain_guidelines-0.0.1-py3-none-any.whl
| Download URL | langchain_guidelines-0.0.1-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e30ec0744aa06a8e02c25485d100d2f52165514f86693766b42153ed89a3b03
|
|
BLAKE2b-256 checksum How to use checksums |
c70ec80ab76360d2d16a0bb21c0fa7cc4bf61a4523b7e3e21b4f9d9c78bf0910
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for langchain-guidelines 0.0.1
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.
