Skip to content

feat(check): honor Yarn project resolutions - #17

Merged
aldegad merged 1 commit into
mainfrom
plan/yarn-resolution-aware-check
Jul 22, 2026
Merged

feat(check): honor Yarn project resolutions#17
aldegad merged 1 commit into
mainfrom
plan/yarn-resolution-aware-check

Conversation

@aldegad

@aldegad aldegad commented Jul 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • resolve npm approval closures from the actual Yarn project lockfile and root resolutions
  • scope approval-ledger reuse to the canonical project, resolutions, and lockfile context
  • fail closed when the project resolution graph cannot be materialized
  • document the closure evidence and approval-isolation contract in English and Korean

Verification

  • npm test
  • git diff --check
  • staged gitleaks secret scan

Regression coverage

  • patched Next closure with Sharp 0.35.3 and PostCSS 8.5.21 is approved from the actual project graph
  • unsafe or missing-resolution project context remains denied
  • approval from one Yarn project cannot authorize another project

@aldegad aldegad left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Independent orchestration review.

Reviewed the project-scoped Yarn closure, context-keyed ledger behavior, PreToolUse context enforcement, safe/unsafe regression fixtures, and English/Korean documentation mirrors. npm test passed locally; GitHub CI passed on Ubuntu and macOS; staged secret scan and git diff --check passed.

The implementation preserves fail-closed behavior when a project closure is absent or vulnerable and prevents approval reuse across project contexts.

@aldegad
aldegad merged commit f08212f into main Jul 22, 2026
2 checks passed
@aldegad
aldegad deleted the plan/yarn-resolution-aware-check branch July 22, 2026 04:53
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