Skip to content

docs: add security policy#18

Merged
NhanAZ merged 1 commit into
mainfrom
agent/security-policy
Jun 9, 2026
Merged

docs: add security policy#18
NhanAZ merged 1 commit into
mainfrom
agent/security-policy

Conversation

@NhanAZ

@NhanAZ NhanAZ commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

What changed

Added a repository security policy that documents supported versions, the private vulnerability reporting channel, required report details, response targets, and coordinated disclosure expectations. Added a Security section to the README linking to the policy.

Why

The repository had no documented process for reporting vulnerabilities, despite project guidance requiring private disclosure. GitHub private vulnerability reporting is enabled, so contributors now have a clear and functional confidential channel.

Testing

  • npm run build - passed.
  • npm test - passed; 62 tests passed.
  • npm run lint - passed.
  • npm run prepublishOnly - passed; build succeeded and 62 tests passed.
  • node bin/opk scan src/cli --json - passed with 0 findings.
  • npm run scan - exited 1 with the existing 18 errors and 33 warnings from repository fixtures and rule definitions.
  • npm pack --dry-run --json - passed with 43 package files.
  • Verified that GitHub private vulnerability reporting is enabled and that the README link resolves to SECURITY.md.

Risks

The response targets are maintainer goals rather than service-level guarantees. Supported-version declarations must be updated when the next minor version is released.

Follow-up

Update the supported versions table when OpenPolicyKit 0.4.0 is released.

@NhanAZ NhanAZ marked this pull request as ready for review June 9, 2026 19:55
@NhanAZ NhanAZ merged commit d2fb93c into main Jun 9, 2026
3 checks passed
@NhanAZ NhanAZ deleted the agent/security-policy branch June 9, 2026 19:55
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