Skip to content

Enforce the public repository boundary - #5

Merged
stc93025mn merged 1 commit into
mainfrom
agent/enforce-public-repository-boundary
Jul 22, 2026
Merged

Enforce the public repository boundary#5
stc93025mn merged 1 commit into
mainfrom
agent/enforce-public-repository-boundary

Conversation

@stc93025mn

Copy link
Copy Markdown
Member

What changed

  • Require explicit free standard GitHub-hosted runner labels in public workflows.
  • Reject custom, self-hosted, dynamic, and larger-runner labels.
  • Reject pull_request_target for public repository checks.
  • Reject private MNPPI packages, registries, Git dependencies, actions, and reusable workflows.
  • Reject package credential secrets and package authentication variables.
  • Document the public pull request boundary.

Why

Public repositories must remain safe for untrusted pull requests and forks. They must not receive private MNPPI dependencies or package credentials. Standard GitHub-hosted runners keep public workflow execution free.

Impact

The current four public repositories pass this policy. A new boundary violation will fail the required public security check.

Validation

  • actionlint -shellcheck '' -color=false .github/workflows/public-token-free-security.yml
  • Policy passed against the live default branches of all four public repositories.
  • Negative fixtures detected runner, event, package, registry, Git, reusable workflow, and credential violations.
  • git diff --check

@stc93025mn
stc93025mn marked this pull request as ready for review July 22, 2026 22:39
@stc93025mn
stc93025mn merged commit 218dbb3 into main Jul 22, 2026
4 checks passed
@stc93025mn
stc93025mn deleted the agent/enforce-public-repository-boundary branch July 22, 2026 22:39
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