Skip to content

chore(deps): enforce install-script policy - #135

Merged
KyleJune merged 1 commit into
mainfrom
codex/script-policy-128
Sep 13, 2026
Merged

KyleJune merged 1 commit into
mainfrom
codex/script-policy-128

Conversation

@KyleJune

Copy link
Copy Markdown
Member

Summary

Juniper's install-script permissions named an unused esbuild version in allow and omitted resolved script-bearing versions. Deny all three resolved esbuild versions and the macOS-only fsevents package, with no install scripts allowed.

Changes

  • Remove the stale esbuild allow entry and obsolete watcher/less denials.
  • Port the existing install-script drift checker and its fixture-based tests. It rejects stale entries and installed lifecycle scripts without a decision, and fails closed when the store is missing or unreadable.
  • Run the gate and its tests through deno task check and after frozen installation on Linux, macOS, and Windows CI. Platform-specific scripts are checked where installed.

Testing

The new gate rejected the original policy with the reported stale allow and uncovered esbuild versions, then passed after correction. Frozen installation, full checks, 43 package tests (480 steps), 15 gate test steps, and real minimal/Tailwind production builds passed locally. The lockfile is unchanged.

Closes

Closes #128

@KyleJune
KyleJune merged commit c8b0bbe into main Sep 13, 2026
10 checks passed
@KyleJune
KyleJune deleted the codex/script-policy-128 branch September 13, 2026 17:04
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 0.12.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

allowScripts has drifted from deno.lock: a stale allow for esbuild@0.27.2, two uncovered esbuild copies

1 participant