Skip to content

Security: valory-xyz/agent-ui-monorepo

Security

SECURITY.md

Security Policy

This document outlines security procedures and general policies for the agent-ui-monorepo project.

For supply-chain-specific concerns — dependency hardening, npm-publish compromise response, install-hook auditing, the CI gates that enforce all of this — see SUPPLY-CHAIN-SECURITY.md.

Supported Versions

This repository ships three independently-versioned applications. Only the latest released version of each app receives security updates.

App Release tag pattern Supported version
agentsfun-ui v*-agentsfun Latest released version
babydegen-ui v*-modius, v*-optimus, v*-basius Latest released version
predict-ui v*-omenstrat-trader, v*-polystrat-trader Latest released version

Reporting a Vulnerability

The agent-ui-monorepo team and community take all security bugs in agent-ui-monorepo seriously. Thank you for improving the security of agent-ui-monorepo. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.

Report security bugs by emailing info@valory.xyz.

The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavour to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.

Report security bugs in third-party modules to the person or team maintaining the module.

Disclosure Policy

When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:

  • Confirm the problem and determine the affected versions.
  • Audit code to find any potential similar problems.
  • Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible as a new GitHub Release (each app ships as a build artifact ZIP attached to a tag-triggered release).

Comments on this Policy

If you have suggestions on how this process could be improved please submit a pull request.

There aren't any published security advisories