OpenCTI client for Python
The official OpenCTI Python client helps developers to use the OpenCTI API by providing easy to use methods and utils. This client is also used by some OpenCTI components.
Install
To install the latest Python client library, please use pip:
$ pip3 install pycti
Local development
# Fork the current repository, then clone your fork
$ git clone https://github.com/YOUR-USERNAME/opencti.git
$ cd client-python
$ git remote add upstream https://github.com/OpenCTI-Platform/opencti.git
# Create a branch for your feature/fix
$ git checkout -b [branch-name]
# Create a virtualenv
$ cd client-python
$ python3 -m venv .venv
$ source .venv/bin/activate
# Install the client-python and dependencies for the development and the documentation
$ python3 -m pip install -e .[dev,doc]
# Set up the git hook scripts
$ pre-commit install
# Create your feature/fix
# Create tests for your changes
$ pytest
# Push you feature/fix on Github
$ git add [file(s)]
$ git commit -m "[descriptive message]"
$ git push origin [branch-name]
# Open a pull request
Install the package locally
$ pip install -e .
Documentation
Client usage
To learn about how to use the OpenCTI Python client and read some examples and cases, refer to the client documentation.
API reference
To learn about the methods available for executing queries and retrieving their answers, refer to the client API Reference.
Tests
Install dependencies
$ pip install -r ./test-requirements.txt
pytest is used to launch the tests.
Launch tests
Prerequisite
Your OpenCTI API should be running. Your conftest.py should be configured with your API url, your token, and if applicable, your mTLS cert/key.
Launching
Unit tests
$ pytest ./tests/01-unit/
Integration testing
$ pytest ./tests/02-integration/
Example testing:
OpenCTI must be running
cd examples
# Configure with you local instance of OpenCTI
export OPENCTI_API_URL="http://localhost:4000"
export OPENCTI_API_TOKEN="xxxxxxxxxxxxxxxxxxxxxx"
#Run one example file
python get_indicators_of_malware.py
About
OpenCTI is a product designed and developed by the company Filigran.
1 maintainer
Metadata
1 maintainer
Release files for pycti 7.261021.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 | |
|---|---|---|---|---|
| pycti-7.261021.0.tar.gz | 278.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pycti-7.261021.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 649.7 kB
Release files / pycti-7.261021.0.tar.gz
| Download URL | pycti-7.261021.0.tar.gz |
|---|---|
| Size | 278.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5e1f69cdcea5773524c52b6acc837371dae1fa0b64d75f1f495e87057b62a76
|
|
BLAKE2b-256 checksum How to use checksums |
25c77df6fd57e2e30a9245e7a74b15d81ab896e7f65cc7991f2e333cff8af015
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / pycti-7.261021.0-py3-none-any.whl
| Download URL | pycti-7.261021.0-py3-none-any.whl |
|---|---|
| Size | 371.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5f1bc6af0e57fc987a238577457af7733cbbc717c316ed8fdebd5ece17b7692
|
|
BLAKE2b-256 checksum How to use checksums |
40fca01b36291736503b0b40ea9fc467f71f94f5ce484a193c8972eef753983e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for pycti 7.261021.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.
