1 maintainer
Metadata
1 maintainer
Release files for ragflow 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 | |
|---|---|---|---|---|
| ragflow-0.0.1.tar.gz | 2.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ragflow-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.9 kB
Release files / ragflow-0.0.1.tar.gz
| Download URL | ragflow-0.0.1.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c7be4b3b458503563325ff5654e4afde245688fed31e93821b949245199ba0e
|
|
BLAKE2b-256 checksum How to use checksums |
73d568292806f962aef917673505a0d766a81aa963b05e818009dab1fb1f6be3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.5
|
Release files / ragflow-0.0.1-py3-none-any.whl
| Download URL | ragflow-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb0bc816aaf473f6a3908791187d3492ef92f2a2ff7625deed3a10ce7d1df2dc
|
|
BLAKE2b-256 checksum How to use checksums |
65f9d2e22312e1812c5f971f01289111b8bdadf411d8c2bda969be727cc2021a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.5
|
Security for ragflow 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.
