1 maintainer
Metadata
1 maintainer
Release files for dify-knowledge-pipline 0.1.6
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 | |
|---|---|---|---|---|
| dify_knowledge_pipline-0.1.6.tar.gz | 16.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dify_knowledge_pipline-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.8 kB
Release files / dify_knowledge_pipline-0.1.6.tar.gz
| Download URL | dify_knowledge_pipline-0.1.6.tar.gz |
|---|---|
| Size | 16.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9809f852703844faa5b220471eb94fbb6b9bcab83fb4397855c1cd62832a3916
|
|
BLAKE2b-256 checksum How to use checksums |
9bb2b18c589737b8877edb8fe0de3b24a6e56c8e1188afa4b2829f2685d586b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.11
|
Release files / dify_knowledge_pipline-0.1.6-py3-none-any.whl
| Download URL | dify_knowledge_pipline-0.1.6-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
14805f15b8dae85dc692387e521a39130170c8b40de6a6f654eec6b721f77498
|
|
BLAKE2b-256 checksum How to use checksums |
b5fdad6580414b1501253ae5aa9a588f958fb782ad70962f7fe959525b8caa4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.10.11
|
Security for dify-knowledge-pipline 0.1.6
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.
