Skip to content

Scorecard: Pinned-Dependencies (5/10) #439

Open

Description

@don-petry

OpenSSF Scorecard Finding

Check: Pinned-Dependencies
Score: 5 / 10
Finding: dependency not pinned by hash detected -- score normalized to 5

Remediation

https://github.com/ossf/scorecard/blob/c395761df6afe1a69e476bc60a013a94bcbc153f/docs/checks.md#pinned-dependencies

Context

This issue was automatically created from an OpenSSF Scorecard scan on 2026-07-14.

Activity

  1. don-petry commented on Jul 20, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  2. don-petry commented on Jul 27, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  3. don-petry commented on Aug 3, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  4. don-petry commented on Aug 10, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  5. don-petry commented on Aug 17, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  6. don-petry commented on Aug 24, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  7. don-petry commented on Aug 31, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  8. don-petry commented on Sep 7, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  9. don-petry commented on Sep 14, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  10. don-petry commented on Sep 21, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  11. don-petry commented on Sep 28, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  12. don-petry commented on Oct 5, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  13. don-petry commented on Oct 12, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  14. don-petry commented on Oct 19, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  15. don-petry commented on Oct 20, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  16. don-petry commented on Oct 26, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  17. don-petry commented on Nov 2, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  18. don-petry commented on Nov 9, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

  19. don-petry commented on Nov 10, 2026

    @don-petry
    CollaboratorAuthor

    Dev-Lead Implementation Plan

    Issue: #439 — Scorecard: Pinned-Dependencies (5/10)

    Scope

    Investigation only. I'm not changing any code: every dependency Scorecard can still flag is a sanctioned exception, and the org standard says those lines must not be edited.

    Findings (audit of main @ 773a6c4)

    • Third-party actions: all 22 uses: refs under .github/workflows/ are pinned to a full 40-char commit SHA. Nothing left to fix.
    • Package installs in workflows: every install is npm ci against the committed package-lock.json, which Scorecard treats as pinned. Playwright runs through npm exec --no, so it uses the lockfile version. I found no pip install, npm install -g, go install, curl | sh or Dockerfile FROM without a digest.
    • What still lowers the score: 13 thin caller stubs call first-party reusable workflows pinned to moving channel tags (e.g. combsmith/.github/...@agent-shield/v2-stable, combsmith/.github-private/...@dev-lead/v139-stable). Scorecard counts every non-SHA ref as "not pinned by hash", whoever owns it.
      • These are the documented "Release channel tags & the mutable-ref exception" in the org AGENTS.md. Each stub's header says "You MUST NOT change the uses: ref". The stubs must match the combsmith/.github standards templates exactly (template-drift is enforced). The tags are protected by the release-channel-tags ruleset.
      • Pinning them to SHAs here would break central channel promotion, cause template drift in this repo, and conflict with the org standard. So this repo cannot fix it on its own.

    Implementation Checklist

    • Audit all workflow uses: refs and install commands
    • No source or workflow changes (see above)

    Tests to Write

    • None. No behavior change.

    Recommendation (needs a maintainer decision)

    1. Accept the risk and close as won't-fix: 5/10 is the expected ceiling while the channel-tag model is in place. or
    2. Make an org-level standards change in combsmith/.github, e.g. caller stubs pin by SHA with a # <channel> comment and the Release Manager rewrites the SHAs on promotion. That has to happen upstream, not in this repo.

    Optional, separate from this issue: ci-failure-analyst.yml still uses the legacy bare-tier pin @ci-failure-analyst/stable. The org AGENTS.md now treats that form as deprecated and as a failure in its pin-compliance check (#1493). Switching it to the major-scoped v<N>-stable form is a re-seed from the standards template. It won't change this Scorecard result.

    Test Command

    npm test / npm run check. Nothing changes, so there is nothing new to run.

  20. don-petry commented on Nov 16, 2026

    @don-petry
    CollaboratorAuthor

    Weekly update: Score is now 5/10. Finding: dependency not pinned by hash detected -- score normalized to 5

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

    dev-leadFor dev-lead agent pickupscorecardOpenSSF Scorecard finding

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions