Skip to content
Ryft
Features How it works See it in action Pricing Download Get Ryft

Ryft › Legal › Third-Party Software Notices and Attributions

Ryft — Third-Party Software Notices and Attributions

Last updated: October 6, 2026

This document provides notices and attributions for third-party software that is distributed with the Ryft desktop application by Ryft Security, LLC ("Ryft," "we"). It is provided to satisfy the attribution and license-notice obligations of the open-source components incorporated into Ryft.

The shipped Ryft desktop application bundles exactly one third-party runtime component — Electron — together with the components Electron itself incorporates. Ryft's own detection engine is implemented entirely in the Python Standard Library and bundles no third-party Python packages. Build-time tooling is not distributed with the application and therefore requires no end-user attribution.

Where a component ships its own complete license manifest inside the application bundle, that in-bundle manifest is the authoritative and complete set of attributions for that component. This document summarizes the notices and points you to those manifests.


Electron

The Ryft desktop application is built on Electron (version ^44.4.5), which is licensed under the MIT License.

Electron incorporates Chromium (licensed under the BSD-3-Clause license and numerous other open-source licenses) and Node.js (licensed under the MIT License, together with the licenses of its own dependencies). The complete, authoritative attributions and license texts for the Chromium, Node.js, and other open-source components that Electron incorporates are reproduced in the consolidated license manifest file that Electron ships inside the application bundle (for example, LICENSES.chromium.html, together with the LICENSE and LICENSES files). That in-bundle manifest is distributed with the Ryft application and is the authoritative, complete attribution for those Chromium, Node.js, and other third-party components. Please refer to it for the full set of component license texts and copyright notices.

MIT License (Electron)

``` Copyright (c) Electron contributors Copyright (c) 2013-2020 GitHub Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ```

For the full attributions covering Chromium (BSD-3-Clause and numerous other open-source licenses) and Node.js (MIT and its dependencies), see the Electron LICENSES manifest included within the distributed Ryft application resources, as described above.


Python Standard Library

The Ryft detection engine is implemented entirely in the Python Standard Library, which is distributed under the Python Software Foundation License. No third-party Python packages are bundled with the Ryft application.


Build-time tooling

Ryft is packaged using build-time tooling (electron-builder and its dependencies). This tooling is used only to build the application and is not distributed with it. Because it is not shipped to end users, it requires no end-user attribution and is not reproduced here.


Release-time verification

Before each release we run a license audit against the shipped build and include the full open-source license manifest in the distributed application resources. If you believe an attribution here is missing or incorrect, contact us and we will correct it promptly.


Ryft Security, LLC · ryftapi.com


← All legal documents

Ryft

Effortless to drive. Deep by default. Built for APIs.

Features· How it works· See it in action· Compare· Pricing· Download· FAQ· Changelog· About· Report a bug
Terms· Privacy· Acceptable Use· Refunds· All legal

Ryft is an authorized security-testing tool. Only test systems you own or have explicit written permission to assess.

© 2026 Ryft Security, LLC · Runs locally · Your test data stays yours.

click anywhere or press Esc to close