The install command does not pin a dependency version
Source references: 1The installation command does not specify dependency versions. The same command may download different code later, so what you install can differ from what was checked.
A later install may download different code even though the command and this report have not changed.
This is an active installation instruction, and `npm install gsap` does not specify a version. When run, npm may resolve whatever version is available then, so installations at different times can contain different code, reducing reproducibility and exposing the project to future release or supply-chain changes. This does not show that the package is malicious. Users can ask for a tested version and require a lockfile with locked installation.
- ✅ Install everything from the public `gsap` npm package: `npm install gsap`. All plugins are included — import them as `gsap/SplitText`, `gsap/MorphSVGPlugin`, etc.- ❌ Do **not** generate an `.npmrc` with a GreenSock auth token, suggest the private `npm.greensock.com` registry, or tell users to sign up for Club GSAP to access a plugin. Those instructions are outdated.