[](https://travis-ci.org/blockchain-certificates/cert-core) [](https://badge.fury.io/py/cert-core)
# cert-core This python library contains common Blockcerts models and accessors used by other Blockcerts python libraries.
Subpackages:
## cert-model
Parses different versions of Blockcerts JSON files into a common Certificate model.
## cert-store
Blockchain certificate storage. This is used as a library in the cert-viewer project.
The certificate storage interface is [simplekv](https://pypi.python.org/pypi/simplekv/). The default configurations use the FilesystemStore, which is highly recommended if you are getting started. This makes it easier to issue, copy, and view your Blockchain Certificates.
## Certificate Storage Configuration
The certificate storage location can be modified with the following configuration entries in your conf.ini file:
cert_store_type: which key-value backing store to use. Current supported values are: - simplekv_fs: (Default) file system store - simplekv_gridfs: (Advanced) gridfs store
cert_store_path: file system path if using simplekv_fs
mongodb_uri: mongo db uri (including db name) if using simplekv_gridfs
Example File System config:
` cert_store_type = simplekv_fs cert_store_path = ./cert_data `
Example GridFS config (Advanced):
` cert_store_type = simplekv_gridfs mongodb_uri = mongodb://localhost:27017/test `
### Legacy options
Warning
Most users should ignore these instructions, which are only included as a temporary bridge for earlier users of blockcerts. We recommend migrating to the latest version of Blockcerts.
### V1 Aware Certificate Store
Warning: avoid this option unless you are sure you need it. Earlier versions of the Blockchain Certificate required a separate storage of the certificate transaction id. That was managed in a certificates mongo db table.
The –v1_aware flag allows support for these certificates.
## Running the python code locally
Ensure you have an python environment. [Recommendations](https://github.com/blockchain-certificates/cert-issuer/blob/master/docs/virtualenv.md)
Git clone the repository and change to the directory
`bash git clone https://github.com/blockchain-certificates/cert-core.git && cd cert-core `
Run cert-core setup
`bash pip install . `
## Unit tests
This project uses tox to validate against several python environments.
Ensure you have an python environment. [Recommendations](https://github.com/blockchain-certificates/cert-issuer/blob/master/docs/virtualenv.md)
- Run tests
` ./run_tests.sh `
## Publishing package to pypi
[First time info](http://peterdowns.com/posts/first-time-with-pypi.html)
Publish script: ./release_package.sh
## Contact
Contact us at [the Blockcerts community forum](http://community.blockcerts.org/).
Metadata
Release files for cert-core 3.0.0
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 |
|---|---|---|---|---|
| cert-core-3.0.0.tar.gz | 14.5 kB | Without provenance | Details for cert-core-3.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cert_core-3.0.0-py3-none-any.whl | Python 3 | none | any | Details for cert_core-3.0.0-py3-none-any.whl |
Total release size: 30.0 kB
Release files / cert-core-3.0.0.tar.gz
| Download URL | cert-core-3.0.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f6c37e18e24eec5f39fe482c0c0643e42da2c121648387fb197da0e312df0008
|
|
BLAKE2b-256 checksum How to use checksums |
a3e672cc14978c21e850670821e1a86c0ae082af9ff2e83e1bac420d24002b89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.28.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.9
|
Release files / cert_core-3.0.0-py3-none-any.whl
| Download URL | cert_core-3.0.0-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6cbea47e33a1f0aae4637dba002d897a281e4a7c2e4d593427745a00fc8a5280
|
|
BLAKE2b-256 checksum How to use checksums |
aeaa94d75004a1420bca6cf5e0d5b702a769add58fb0457abf87c1e974000cfe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.28.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.9
|
Security for cert-core 3.0.0
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.