1 maintainer
Metadata
1 maintainer
Release files for dify-knowledge-pipeline 0.1.7
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_pipeline-0.1.7.tar.gz | 16.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dify_knowledge_pipeline-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 34.2 kB
Release files / dify_knowledge_pipeline-0.1.7.tar.gz
| Download URL | dify_knowledge_pipeline-0.1.7.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
53a3e7516491708988e3ab7e09a453b8f6a804b1618f655a9e2382fcf29a9c44
|
|
BLAKE2b-256 checksum How to use checksums |
a7e3974076e38f8d724ee0a5819ea022144735b87905afbdfb7ab2943e629986
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Release files / dify_knowledge_pipeline-0.1.7-py3-none-any.whl
| Download URL | dify_knowledge_pipeline-0.1.7-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e517642f15f7ae7b924e35451d8c257f46b5953f94da7bc8995bc20f34e822e
|
|
BLAKE2b-256 checksum How to use checksums |
d8df3fbe9dd7a18b480063796274d58ff0727b2d72fe753e478c84491ef47281
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.11
|
Security for dify-knowledge-pipeline 0.1.7
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.
