A previous release had provenance metadata, but this release does not. View details.
ashare-lake has moved to CNEquity
This project has been renamed. ashare-lake is no longer updated —
all future development happens under the new name.
pip install cnequity
- Repository: https://github.com/rootSunc/CNEquity
- PyPI: https://pypi.org/project/cnequity/
- CLI:
cne(wasasl) · Python import:from cnequity...(wasfrom ashare_lake...)
The last functional release under this name is ashare-lake==0.6.0. This
0.6.1 release changes nothing except this notice.
Metadata
Release files for ashare-lake 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ashare_lake-0.6.1.tar.gz | 681.4 kB | Without provenance | Details for ashare_lake-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ashare_lake-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for ashare_lake-0.6.1-py3-none-any.whl |
Total release size: 1.5 MB
Security for ashare-lake 0.6.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.
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 0.6.0 2 files With provenance
- Added 0.6.1 2 files 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.