This release is a pre-release and may not be stable for production use.
UNKNOWN
Metadata
Release files for plone.intelligenttext 1.0-beta1
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 | |
|---|---|---|---|---|
| plone.intelligenttext-1.0-beta1.tar.gz | 9.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| plone.intelligenttext-1.0_beta1-py2.4.egg | Legacy Egg format | - | - | Details |
Total release size: 17.3 kB
Release files / plone.intelligenttext-1.0-beta1.tar.gz
| Download URL | plone.intelligenttext-1.0-beta1.tar.gz |
|---|---|
| Size | 9.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fff69ab457a4694e7629278e6e9b3809472dbf506818308d10b23bcb7d102f57
|
|
BLAKE2b-256 checksum How to use checksums |
c52d5037e24c00bab9f5330c3be2f2461a693375de3e7233b8601417b5caee10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / plone.intelligenttext-1.0_beta1-py2.4.egg
| Download URL | plone.intelligenttext-1.0_beta1-py2.4.egg |
|---|---|
| Size | 7.7 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
9c24c171707f7c64f5ea5b0bcb97db1e8e14d40a30960692c75982602382ca48
|
|
BLAKE2b-256 checksum How to use checksums |
d8fafab094f9e4ae4d4ca5d4253f23b444f5ffb9c8d48e8603eed046b9b03020
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for plone.intelligenttext 1.0-beta1
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.