Cryptolytics
Fundamental analysis for blockchain and crypto projects
Getting Started • Features • Documentation • Support • Report a Bug • Contribution • Changelog
Calculate quality scores for open-source blockchain and crypto projects based on developer and social activity. Metadata is collected from a variety of different data sources. The goal is to get a list of the best projects for long-term investment based on the current project fundamentals.
Highlights
TBD
Getting Started
TBD
Support & Feedback
Please understand that we won't be able to provide individual support via email. We also believe that help is much more valuable if it's shared publicly so that more people can benefit from it.
| Type | Channel |
|---|---|
| 🚨 Bug Reports | |
| 🎁 Feature Requests | |
| 👩💻 Usage Questions | |
| 📢 Announcements |
Features
TBD
Documentation
TBD
Contribution
- Pull requests are encouraged and always welcome. Read our contribution guidelines and check out help-wanted issues.
- Submit Github issues for any feature request and enhancement, bugs, or documentation problems.
- By participating in this project, you agree to abide by its Code of Conduct.
- The development section below contains information on how to build and test the project after you have implemented some changes.
Development
To build the project and run the style/linter checks, execute:
pip install universal-build
python build.py --make --check
Alternatively, you can also run all necessary steps (build, check, test, and release) within a containerized environment by executing the following in the project root folder (this requires Docker and Act):
act -b -j build
Refer to our contribution guides for more detailed information on our build scripts and development process.
Licensed MIT.
Metadata
Release files for cryptolytics 0.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 | Actions |
|---|---|---|---|---|
| cryptolytics-0.1.1.tar.gz | 8.6 kB | Without provenance | Details for cryptolytics-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cryptolytics-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for cryptolytics-0.1.1-py3-none-any.whl |
Total release size: 14.6 kB
Release files / cryptolytics-0.1.1.tar.gz
| Download URL | cryptolytics-0.1.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea30c45316934b99aaf47c1bfe9b0190a32ceec67155b96fb9450e49a9644d75
|
|
BLAKE2b-256 checksum How to use checksums |
da12db13631eb42b33e5f3f4d07afebf005703bb69d4923cbe1c593884a22b2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.7.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Release files / cryptolytics-0.1.1-py3-none-any.whl
| Download URL | cryptolytics-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1e830aaa34efa81d39303c924f37d6bb7e463f275df3c798de397a021675f00
|
|
BLAKE2b-256 checksum How to use checksums |
c1a59d4a4f551c3677567c62920df75ac2cfd987d54f53b6f82c2685ad1bb06f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.7.1 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for cryptolytics 0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.