Socket.dev installScripts vs gitHubDependency alerts - expected behavior vs real risk

TL;DR

Per the Socket.dev case study: install scripts are often legitimate; direct GitHub dependencies should be pinned or replaced with registry versions.

Steps

1. Per the Socket.dev case study: install scripts are often legitimate; direct GitHub dependencies should be pinned or replaced with registry versions.

When to use

Use this skill when you run into "Socket.dev installScripts vs gitHubDependency alerts - expected behavior vs real risk".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Problem: Two alert types need different responses. installScripts on electron is expected behavior - the package needs a postinstall script to download its binary. gitHubDependency is a real risk signal: the package depends directly on a GitHub repo that could be deleted or rewritten - check whether an npm release exists and switch to it, or pin to a specific commit.

Verified resolution: Per the Socket.dev case study: install scripts are often legitimate; direct GitHub dependencies should be pinned or replaced with registry versions.

Source URL: https://github.com/miccy/dont-be-shy-hulud/blob/HEAD/packages/docs-content/reference/case-study-socket.md