Documentation: https://recordedfuture-professionalservices.github.io/psengine/
Github: https://github.com/RecordedFuture-ProfessionalServices/psengine
PyPi: https://pypi.org/project/psengine/
PSEngine is a simple, yet elegant, library for rapid development of integrations with Recorded Future.
PSEngine allows you to interact with the Recorded Future API extremely easily. There’s no need to manually build the URLs and query parameters, just use the modules dedicated to individual API endpoints.
PSEngine is a Python package solely built and maintained by the Recorded Future Cyber Security Engineering team powering a number of high profile integrations, such as: PS Banshee; Recorded Future Alerts for QRadar; Anomali ThreatStream: Alerts and Analyst Notes integrations; Google SecOps and many more.
Installation
PSEngine is a Python package that can be installed using pip. To install PSengine, run the following command:
pip install psengine
PSEngine officially supports Python >= 3.10, < 3.15.
Supported Features & Best Practices
PSEngine is ready for the demands of building robust and reliable integrations.
It can easily interact with the following Recorded Future datasets:
- Analyst Notes
- Attack Surface Intelligence
- Collective Insights
- Classic & Playbook Alerts
- Detection Rules
- Fusion File management
- Identity Exposures management
- List management
- Malware Intelligence (including Auto Yara and Auto Sigma)
- Malware Sandbox reports download
- On demand IOC enrichment
- Risklists
- Risk History
- Sandbox Detonation of files and URLs
- STIX conversion
And facilitate the development with features like:
- Built-in logging
- Easy configuration management
- Markdown creation from certain data types
- Proxy support
Previous versions and version documentation
PSEngine has been made public from our internal version 2.0.4. Previous versions, including version 1, are not publicly available.
The documentation arrived at version 2.1.1. Older versions are not explicitly documented and changes can be found in the Release History section.
Contributing
See CONTRIBUTING.md for development setup, code standards, testing conventions, and the CI workflow.
1 maintainer
Release files for psengine 2.13.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 | |
|---|---|---|---|
| psengine-2.13.0.tar.gz | 185.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| psengine-2.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 520.7 kB
Release files / psengine-2.13.0.tar.gz
| Download URL | psengine-2.13.0.tar.gz |
|---|---|
| Size | 185.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f1823c026edd6a6cff8c5044fd4894f385c483aba51431e18810bf84485b1206
|
|
BLAKE2b-256 checksum How to use checksums |
86839e0bee0f0c8933e082f310b2fc7a623789d1181e5bcf5b163ba4f89683ea
|
| 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 10, 2026.
Transparency logRelease files / psengine-2.13.0-py3-none-any.whl
| Download URL | psengine-2.13.0-py3-none-any.whl |
|---|---|
| Size | 335.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
228b3121102aae5ec494e67d25d57fb072c9fb4341a91e258a9bea0ddf347457
|
|
BLAKE2b-256 checksum How to use checksums |
cbbb78e6b8022285c51df906e335e9b974f2f5aaf675e5dfad6bb9494652991a
|
| 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 10, 2026.
Transparency log
