py-vibracore
Public python SDK for the CEMS VibraCore web-API
This repository is created by CEMS BV and is a public python wrapper around the CEMS VibraCore web-API.
Installation
To install a package in this repository run:
$ pip install py-vibracore
ENV VARS
To use py-vibracore add the follow ENV vars to your environment. Or provide
them when asked.
* NUCLEI_TOKEN
- Your NUCLEI user token
You can obtain your NUCLEI_TOKEN on NUCLEI. Go
to personal-access-tokens and create a new user token.
Contribution
Environment
We recommend developing in Python3.9 with a clean virtual environment (using
virtualenv or conda), installing the requirements from the requirements.txt
file:
Example using virtualenv and pip to install the dependencies in a new
environment .env on Linux:
python -m venv .env
source .env/bin/activate
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install -e .
Documentation
Build the docs:
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install .
sphinx-build -b html docs public
Format
We format our code with black and isort.
black --config "pyproject.toml" src/pyvibracore tests notebooks
isort --settings-path "pyproject.toml" src/pyvibracore tests notebooks
Lint
To maintain code quality we use the GitHub super-linter.
To run the linters locally, run the run_super_linters.sh bash script from the
root directory.
UnitTest
Test the software with the use of coverage:
python -m pip install --upgrade pip setuptools
pip install -r requirements.txt
pip install -e .
coverage run -m pytest
Requirements
Requirements are autogenerated by the pip-compile command with python 3.9
Install pip-tools with:
pip install pip-tools
Generate requirements.txt file with:
pip-compile --extra=test --extra=lint --extra=docs --extra=notebook --output-file=requirements.txt pyproject.toml
Update the requirements within the defined ranges with:
pip-compile --upgrade --extra=test --extra=lint --extra=docs --extra=notebook --output-file=requirements.txt pyproject.toml
Metadata
Release files for py-vibracore 0.3.2
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 |
|---|---|---|---|---|
| py_vibracore-0.3.2.tar.gz | 20.5 kB | With provenance | Details for py_vibracore-0.3.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| py_vibracore-0.3.2-py3-none-any.whl | Python 3 | none | any | Details for py_vibracore-0.3.2-py3-none-any.whl |
Total release size: 46.3 kB
Release files / py_vibracore-0.3.2.tar.gz
| Download URL | py_vibracore-0.3.2.tar.gz |
|---|---|
| Size | 20.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b8ca891da6c8143bd0b75a549201e8fbeefea48c55141e6772fb021bc6b0bcad
|
|
BLAKE2b-256 checksum How to use checksums |
65004c0e1d61b77c0ae9a98e0d0bf965573c5c136e4a3bee0edcc5f9bd744fbd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / py_vibracore-0.3.2-py3-none-any.whl
| Download URL | py_vibracore-0.3.2-py3-none-any.whl |
|---|---|
| Size | 25.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
740408218997c4779efe155b8b6b1c811514d2dc3990b791dd09f8171ac93eee
|
|
BLAKE2b-256 checksum How to use checksums |
cadd78318dd52afb80a42efd061715dbd063d5d6345c2606f85b3473e12f88e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logSecurity for py-vibracore 0.3.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for py_vibracore-0.3.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logA 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.