Skip to content

docs(security): add vulnerability reporting policy - #98

Merged
utpalsinghdev merged 1 commit into
mainfrom
docs/security-policy
Nov 20, 2026
Merged

utpalsinghdev merged 1 commit into
mainfrom
docs/security-policy

Conversation

@utpalsinghdev

Copy link
Copy Markdown
Owner

Summary

Open Canvas did not tell people where to report a vulnerability without opening a public issue. SECURITY.md gives reporters a private email address, explains what to include and redact, and identifies the latest stable release as the target for security fixes.

What users will see

The README and contribution guide now link to the security policy. Regular bugs still go to GitHub Issues. There are no editor, MCP, or runtime changes.

Affected areas

  • Contributor tooling or documentation

Acceptance criteria

  • Contributors can find the policy from both the README and contribution guide. Both links point to the new root SECURITY.md.
  • The policy directs reports to the maintainer's published contact email rather than a public issue or an unavailable GitHub reporting form.

Verification

  • git diff --cached --check passed. Checked both links to SECURITY.md, confirmed the reporting address against the maintainer's public contact page, and confirmed the latest-release link returns HTTP 200.
  • corepack pnpm install --frozen-lockfile, corepack pnpm run check, corepack pnpm run build, and corepack pnpm run changeset:status --since=origin/main passed.

@utpalsinghdev
utpalsinghdev merged commit bb0af51 into main Nov 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant