chore: add security policy, Dependabot config, and dependency review

.github/dependabot.yml

@@ -0,0 +1,13 @@
+version: 2
+updates:
+  - package-ecosystem: "bun"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      minor-and-patch:
+        update-types: ["minor", "patch"]
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/dependency-review.yml

@@ -0,0 +1,19 @@
+name: Dependency review
+
+on:
+  pull_request:
+    branches: [main]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  dependency-review:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/dependency-review-action@v4
+        with:
+          fail-on-severity: high
+          comment-summary-in-pr: on-failure

SECURITY.md

@@ -0,0 +1,38 @@
+# Security Policy
+
+## Reporting a vulnerability
+
+Please do **not** open a public issue for security problems.
+
+Report privately through GitHub's private vulnerability reporting:
+https://github.com/ojspace/soloteam-cli/security/advisories/new
+
+You will get an acknowledgement within 7 days. Once the report is confirmed,
+a fix is prioritised and an advisory is published together with the patched
+release. Please give us a reasonable window to ship a fix before public
+disclosure.
+
+## Scope
+
+In scope:
+
+- Code in this repository on the default branch and in published releases
+- Supply-chain issues in dependencies declared here that are exploitable
+  through this project
+
+Out of scope:
+
+- Vulnerabilities in third-party services or tools this project only calls
+- Issues that require a compromised local machine or already-elevated access
+- Findings from automated scanners without a demonstrated impact
+
+## What to include
+
+- Affected version or commit
+- Steps to reproduce, or a proof of concept
+- Impact: what an attacker can do
+- Any suggested mitigation
+
+## Supported versions
+
+Only the latest release receives security fixes.