The author of this package has not provided a project description
Metadata
Release files for quadkit-ai-memory 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 | |
|---|---|---|---|---|
| quadkit_ai_memory-0.0.1.tar.gz | 390 Bytes | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| quadkit_ai_memory-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 kB
Release files / quadkit_ai_memory-0.0.1.tar.gz
| Download URL | quadkit_ai_memory-0.0.1.tar.gz |
|---|---|
| Size | 390 Bytes |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79a547f20399a4ae6b9e5450386721e2541d95169c74f0e637f5b1417aa53de6
|
|
BLAKE2b-256 checksum How to use checksums |
5852b089aeec64f565698597126e58793799d78158b88b067608b999f06163bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / quadkit_ai_memory-0.0.1-py3-none-any.whl
| Download URL | quadkit_ai_memory-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27c518780cc475e17ef65eef5fb873f2a5d4b7bebb0c3a2acd9780b0f415ae7d
|
|
BLAKE2b-256 checksum How to use checksums |
3c9ee19e37316e93c61b1c354d56fd2c8abae70c09b826cc9a2cee81da8d752c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for quadkit-ai-memory 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.