This package has been deprecated. Please use 'kinetic-core' instead.
Metadata
Release files for salesforce-toolkit 1.1.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 | |
|---|---|---|---|---|
| salesforce_toolkit-1.1.1.tar.gz | 380.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| salesforce_toolkit-1.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 383.0 kB
Release files / salesforce_toolkit-1.1.1.tar.gz
| Download URL | salesforce_toolkit-1.1.1.tar.gz |
|---|---|
| Size | 380.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4b9ef3b7ac59ea8ff7a395309735fa3f89c2c10d76dea98d2f7a96f5b23e53b
|
|
BLAKE2b-256 checksum How to use checksums |
5266c56b613a28d5bd88480cae4aceaf0663b3843a3b869f35f88ab94810141e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / salesforce_toolkit-1.1.1-py3-none-any.whl
| Download URL | salesforce_toolkit-1.1.1-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6484558dd630c8268be05ae07f7a7e1078c8c748f78bd801bc85164b89a78b5f
|
|
BLAKE2b-256 checksum How to use checksums |
bb614d4bb511859075b925a380abd4711c25b23711bc1f7d635c7ff69ece4348
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for salesforce-toolkit 1.1.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.