Security: Disable yarn postinstall scripts

[ChristopherChudzicki]

This PR was generated automatically via a script.

This PR disables yarn's postinstall scripts by setting ignore-scripts true in .yarnrc.

Why this change?

Disabling postinstall scripts improves security by:

• Preventing malicious code execution: Stops potentially harmful scripts from running during package installation
• Supply chain security: Reduces risk from compromised packages that could execute malicious postinstall scripts
• Controlled execution: Allows manual review and execution of necessary scripts only when needed

What changed?

• Added ignore-scripts true to .yarnrc

Impact

• Some packages may require manual script execution if they depend on postinstall hooks
• Improved security posture against supply chain attacks
• No functional changes to core application code

This is a security best practice recommended for production applications to prevent potential malicious code execution during package installation.

[gemini-code-assist]

Summary of Changes

Hello @ChristopherChudzicki, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the project's security by disabling yarn's postinstall scripts. This proactive measure prevents the automatic execution of potentially malicious code during package installations, thereby mitigating risks associated with supply chain attacks and ensuring a more controlled and secure environment for dependency management. While some packages might require manual script execution, the overall impact is a stronger security posture without affecting core application functionality.

Highlights

• Security Enhancement: Disables yarn postinstall scripts to prevent malicious code execution during package installation.
• Supply Chain Security: Reduces risk from compromised packages by preventing the automatic execution of potentially malicious postinstall scripts.
• Controlled Execution: Ensures that necessary scripts are run manually, allowing for review and intentional execution.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request enhances security by disabling yarn post-install scripts, which is a commendable security hardening practice. The implementation is correct. However, this change will have a significant side effect on the development workflow. Specifically, it will prevent the flow-bin package from installing its required binary, causing the npm run flow script to fail. This is a crucial detail to consider before merging.

[gemini-code-assist]

While disabling post-install scripts is a good security measure, it's important to be aware of the direct consequences for this project's development setup. The flow-bin dev dependency relies on a postinstall script to download the appropriate Flow binary. By setting ignore-scripts true, this script will be blocked.

As a result, the flow binary will not be installed, and the npm run flow command, which is part of the project's scripts in package.json, will fail. This will break the type-checking workflow for developers contributing to this library.

Before merging, the team should decide on a mitigation strategy, such as:

• Manually running the flow-bin installation script after yarn install.
• Documenting this new manual step for developers.
• Finding an alternative method to install and manage the Flow binary.