Skip to content

chore(security): tighten Claude workflow trust boundary and permissions #1280

@ggfevans

Description

@ggfevans

Parent

Part of #1276

Summary

Tighten Claude automation trigger trust boundaries and apply least-privilege permissions.

Problem

Current trigger/permission scope is broad enough that external contributor interactions may invoke privileged automation paths.

Acceptance Criteria

  • Reassess and tighten event author-association allowlist for claude.yml.
  • Reduce job permissions to minimum required (contents, issues, pull-requests, etc.).
  • Add explicit guardrails for untrusted contexts (forks, contributor-triggered events).
  • Document trigger policy and expected maintainer usage.
  • Verify no regression for intended maintainer workflows.

Notes

Target practical security hardening with minimal maintainer friction.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions