# GitHub Actions composite action cannot access secrets directly

> Fix the GitHub Actions error where a composite action references the secrets context directly, which is not available inside composite actions.

Source: https://latchkey.dev/learn/github-actions/github-actions-composite-action-cannot-access-secrets  
Updated: 2026-06-26

Composite actions cannot read the secrets context directly; only the calling workflow can. A composite action that references secrets.* gets an unrecognized context error or an empty value - secrets must be passed in as inputs.

## Diagnose it: what token do you actually have?

Permission failures in Actions are almost never about your repository settings alone. Three things combine: the default `GITHUB_TOKEN` permission set for the repo or organization, the `permissions:` block in the workflow, and whether the event is a fork pull request, which downgrades the token to read-only regardless of everything else.

```.github/workflows/ci.yml
- name: Show the token scopes actually granted
  run: |
    curl -sI -H "Authorization: Bearer $GITHUB_TOKEN" \
      https://api.github.com/ | grep -i "^x-oauth-scopes\|^x-accepted"
    echo "event: ${{ github.event_name }}"
    echo "fork PR: ${{ github.event.pull_request.head.repo.fork }}"
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
```

> If `fork PR` prints `true`, stop looking at `permissions:`. A fork pull request gets a read-only token by design, and no workflow-level grant can raise it.

## Grant the narrowest permission that works

Declaring a `permissions:` block switches the job from the repository default to exactly what you list, so an incomplete block is a common cause of a new failure right after someone tightened security. List every scope the job needs, not just the one that failed.

```.github/workflows/ci.yml
permissions:
  contents: read        # checkout
  packages: write       # push to GHCR
  id-token: write       # OIDC to a cloud provider
  pull-requests: write  # comment on or label a PR
  checks: write         # publish check runs
```

> Set `permissions` at the job level rather than the workflow level where you can. A workflow-level grant applies to every job, including ones that only run tests.

## FAQ

### What causes GitHub Actions composite action cannot access secrets directly?

direct secrets reference inside composite. The composite action body references secrets.NPM_TOKEN, but the secrets context is not exposed to composite actions.

### How do I fix GitHub Actions composite action cannot access secrets directly?

Pass the secret in as an input. Declare an input on the composite action for the secret value.

### What does GitHub Actions composite action cannot access secrets directly actually mean?

A composite action fails validation referencing secrets.*, or a secret it expected is empty at runtime.

### How do I stop GitHub Actions composite action cannot access secrets directly happening again?

Pass secrets into composite actions as explicit inputs. The prevention section lists 2 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt