A previous release had provenance metadata, but this release does not. View details.
This release is a pre-release and may not be stable for production use.
superdoc-sdk-cli-linux-arm64
Platform companion package for superdoc-sdk.
This package is automatically installed by superdoc-sdk via PEP 508 environment markers — you do not need to install it manually.
For air-gapped or private index environments, mirror both superdoc-sdk and the superdoc-sdk-cli-* package for your platform.
4 maintainers
Metadata
4 maintainers
Release files for superdoc-sdk-cli-linux-arm64 2.0.0.dev100
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| superdoc_sdk_cli_linux_arm64-2.0.0.dev100-py3-none-any.whl | Python 3 | none | any | Details for superdoc_sdk_cli_linux_arm64-2.0.0.dev100-py3-none-any.whl |
Release files / superdoc_sdk_cli_linux_arm64-2.0.0.dev100-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | superdoc_sdk_cli_linux_arm64-2.0.0.dev100-py3-none-any.whl |
|---|---|
| Size | 40.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e25c5027fe9c21bce167262a12beba6dc29bf10c1948078ac4c3fde812ad8ff3
|
|
BLAKE2b-256 checksum How to use checksums |
ab1f4cdb41a20cb6597ac9d7d1f684c24b19a6e1ddce9a1074f523f8a17f5d25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.15
|
Security for superdoc-sdk-cli-linux-arm64 2.0.0.dev100
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 1.21.1 1 file With provenance
- Added 2.0.0.dev100 1 file Without provenance
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
