Skip to main content

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.

Metadata

Release files for psengine 2.14.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for psengine 2.14.1
File Size Uploaded Provenance Actions
psengine-2.14.1.tar.gz 198.9 kB With provenance Details for psengine-2.14.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for psengine 2.14.1
File Interpreter ABI Platform Actions
psengine-2.14.1-py3-none-any.whl Python 3 none any Details for psengine-2.14.1-py3-none-any.whl

Total release size: 539.7 kB

Release files / psengine-2.14.1.tar.gz

Download URL psengine-2.14.1.tar.gz
Size 198.9 kB
Tags Source
SHA-256 checksum
How to use checksums
96463127bbaacb95f704695e7afd60696bf3f2af5d17e6a4bd56f2c129ab77ff
BLAKE2b-256 checksum
How to use checksums
aacd938b36ad03941bf592b9af49be8e5ac5b27dd61647de0868c35ecfbfeee4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 18, 2026.

Transparency log

Release files / psengine-2.14.1-py3-none-any.whl

Download URL psengine-2.14.1-py3-none-any.whl
Size 340.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a9e693c520fe63b8ed546e973f2a9d393f66a7ef40e4599ec5ba062fdc822f3e
BLAKE2b-256 checksum
How to use checksums
ceae7493921f03d06cfd292449859adcfc5bd4c7022861e0c5767a6de54ea470
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 18, 2026.

Transparency log

Security for psengine 2.14.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for psengine-2.14.1.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 Nov 18, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

2.14.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page