> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/security.md).

# Security Policy

This file is the concise security policy and reporting entry point for AI OS. The detailed control inventory, compliance notes, open findings, phase history, and audit results live in [docs/SECURITY-COMPLIANCE.md](broken://pages/IjDbQNkb2yWcMjlSb6U8). Keep implementation detail in that ledger and keep reporting guidance here.

## Supported Scope

AI OS is a private, local-first Bun/React project. Security fixes are supported on the current `main` branch. There is no public version support matrix or long-term release schedule for older tags unless a maintainer explicitly opens one.

## Security Model

AI OS is designed for local operator use. Treat credentials, generated runtime artifacts, account-auth material, logs, caches, and local environment values as private. The exact artifact list, data flows, source-collection gates, deletion paths, and Trend Finder compliance details are maintained only in the compliance ledger.

## Reporting A Vulnerability

Do not open a public issue containing exploit details, private paths, tokens, logs, generated runtime data, or account-auth material.

Use GitHub private vulnerability reporting or a private security advisory for this repository when available. If no private channel is available, open a minimal public issue that asks for a security contact and omit technical details until a private channel is established.

Useful private report details include:

* affected commit, branch, or package version
* reproduction steps using sanitized data
* expected and actual impact
* whether credentials, local files, generated data, or third-party services are involved
* suggested fix or mitigation, if known

This is a private project, so response and remediation are best-effort rather than a commercial SLA. Accepted issues should be fixed on `main`, documented in the compliance ledger when they affect posture, and verified with the narrowest useful checks.

## Before Sharing Changes

Run the relevant checks for the change. For security-sensitive code or credentialed local runs, include:

```bash
bun audit
bun run runtime:check-private
```

For code changes, also run the project checks requested in the repository guidance, usually `bun run typecheck` and `bun run test`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.