Skip to content

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

chore(security): add vulnerability reporting policy (#164)

Sima Bagheri4ac500a49826
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index f57994bd..3a3b4070 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -2,3 +2,4 @@
/.github/CODEOWNERS @tt-a1i
/.github/workflows/** @tt-a1i
/.github/actions/** @tt-a1i
+/SECURITY.md @tt-a1i
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f610ae32..e8cccd56 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,7 +9,7 @@ Stability comes before feature count. A small change with a real reproduction, a
- Found a renderer, validator, package, or viewer problem? Use [the bug report form](.github/ISSUE_TEMPLATE/bug-report.yml).
- Made a useful real-world diagram? Use [the showcase form](.github/ISSUE_TEMPLATE/showcase.yml).
- Want to change a schema, renderer contract, validation rule, installation path, export, or other product behavior? Open or link an issue before implementing it. Agree on the user value, compatibility boundary, and non-goals first.
-- Found a security vulnerability? Do not publish exploit details or secrets. Use GitHub's private security reporting for this repository.
+- Found a security vulnerability? Follow [the security policy](SECURITY.md). Do not publish exploit details or secrets.
Small documentation corrections and narrowly scoped test fixes do not require a planning issue. Large documentation surfaces do: prefer improving the canonical Skill, contract, diagnostic, or existing guide over creating a second explanation of the same behavior.
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 00000000..d0513681
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,54 @@
+# Security Policy
+
+Archify welcomes responsible security reports. Please report suspected
+vulnerabilities privately so maintainers can investigate and coordinate
+remediation before public disclosure.
+
+## Supported versions
+
+Archify is under active development. Please report vulnerabilities affecting
+the latest stable release or current `main`.
+
+Reports affecting older releases are also welcome. Include the exact version
+or commit so maintainers can determine the affected range. This policy does
+not promise maintenance or backports for older releases.
+
+## Reporting a vulnerability
+
+Use GitHub's private vulnerability reporting for this repository when that
+option is available.
+
+Include, when available:
+
+- the affected Archify version or commit;
+- the installation method, operating system, Node.js version, and relevant
+ host or agent;
+- the affected command, component, or entry point;
+- a minimal reproduction or proof of concept;
+- the security impact and conditions required to reproduce it;
+- a suggested mitigation or workaround, if known.
+
+Use a minimal, redacted reproduction. Do not publish exploit details,
+credentials, access tokens, secrets, private repository content, personal
+data, or customer data in public issues, discussions, pull requests, logs,
+screenshots, generated artifacts, or package tests.
+
+If private vulnerability reporting is unavailable, open a public issue asking
+the maintainers for a private security contact. Do not include vulnerability
+details in that issue.
+
+## Coordinated disclosure
+
+Please keep vulnerability details private while the report is being triaged
+and, when applicable, while a fix is being prepared.
+
+Coordinate public disclosure with the maintainers through the private reporting
+channel so affected users can be given accurate remediation guidance.
+
+## Non-security bugs
+
+Use [the bug report form](.github/ISSUE_TEMPLATE/bug-report.yml) for
+functional, rendering, validation, compatibility, packaging, or documentation
+defects that do not create a security impact.
+
+If you are unsure whether a finding is security-sensitive, report it privately.