Skip to content

security(scorecard): Token-Permissions alert on scorecard.yml is 19 days stale (CSA001/CSA003) #268

Closed

Description

@hyperpolymath

Hypatia code_scanning_alerts CSA001 + CSA003 (both high), surfaced on the #266 scan.

Code scanning (Scorecard): TokenPermissionsID — Token-Permissions — 19 day(s) old [STALE] at .github/workflows/scorecard.yml (threshold: 7 days) — overdue for remediation.

Assessment (verified): genuine, pre-existing (predates the close-out session), independent of any docs change. CSA001 and CSA003 are the same underlying alert (stale + overdue framings). The ledger classifies scorecard.yml under the billing-wall "pattern B" parking, but least-privilege permissions: hardening (the Token-Permissions remediation) is separate from the billing issue and worth doing on its own.

Disposition: owner governance call. Remediation = pin explicit least-privilege permissions: blocks in .github/workflows/scorecard.yml (and confirm the code-scanning alert clears). Not auto-applied — workflow/security changes are deliberate owner actions.

Source: Hypatia neurosymbolic scan on #266.

Activity

  1. added
    choreRoutine maintenance with no behaviour change
    cicdCI/CD: workflows, actions, lockfiles, pins, runners, release gates
    on Aug 27, 2026
  2. hyperpolymath commented on Sep 30, 2026

    @hyperpolymath
    OwnerAuthor

    RULING D180 (2026-09-30T14:22Z) · scope: repo · basis: applied-unless-struck (D113; owner approved the full table, none struck)

    Yes: pin least-privilege permissions in scorecard.yml (read-all top level, job-scoped writes).

    surface: metadatastician/standards#787 (comment)

    The open question in this issue is answered by the ruling above; future agents should act on it rather than re-ask.

  3. hyperpolymath commented on Nov 6, 2026

    @hyperpolymath
    OwnerAuthor

    Resolved by #360, merged as 007d749ec02b3836b45a2183ebbbaf72935c9d91. The explicit least-privilege workflow and refreshed pinned Scorecard caller have now been exercised on main: run 42235492211 succeeded. GitHub reports the specific Scorecard token-permission alert #149 as fixed (also #11 for Hypatia); neither was manually dismissed. This closes this issue's stale Token-Permissions obligation. The remaining Scorecard review-policy/history, fuzzing and Best Practices findings are separate, retained follow-up work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreRoutine maintenance with no behaviour changecicdCI/CD: workflows, actions, lockfiles, pins, runners, release gatespriority:p2Normal - queue itscope:repoConfined to this repositorysecurity

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions