Skip to content

docs: action-layer positioning, recent updates, security email#2

Closed
keirsalterego wants to merge 1 commit into
mainfrom
chore/v0.1.0-release
Closed

docs: action-layer positioning, recent updates, security email#2
keirsalterego wants to merge 1 commit into
mainfrom
chore/v0.1.0-release

Conversation

@keirsalterego

Copy link
Copy Markdown
Contributor

Public positioning updated to the action layer; recent shipped features noted; security contact moved to security@vyrox.dev.

Copilot AI review requested due to automatic review settings June 8, 2026 07:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates public-facing documentation to reflect Vyrox’s positioning as an “action layer,” calls out recently shipped capabilities, and standardizes the security contact email to security@vyrox.dev.

Changes:

  • Updated SECURITY policy contact email to security@vyrox.dev.
  • Refreshed the org profile README positioning + pipeline diagram to include an audit stage and “action layer” messaging.
  • Added a “Recently shipped” blurb and updated the README security contact.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
SECURITY.md Updates vulnerability reporting contact email to the new security inbox.
profile/README.md Updates product positioning, pipeline/audit messaging, and security contact email in quick links.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread SECURITY.md
Do not open a public GitHub issue for security reports.

Email: `sec.vyrox@proton.me`
Email: `security@vyrox.dev`
Comment thread profile/README.md

- Website: [vyrox.dev](https://vyrox.dev)
- Security issues: sec.vyrox@proton.me
- Security issues: security@vyrox.dev
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.

2 participants