T08 · Insecure Dependencies
- Location
README.md:76- Finding
Unpinned npm Package Execution in Installation Instructions
- Content
View full analysis
- Remediation
View remediation
add sirsws/judgment-loop ``` 2. Apply the same pinned version consistently in `README.md` and `README.zh-CN.md`. 3. Document the expected npm package publisher, registry, and reviewed version so users can verify package provenance before execution. 4. Where supported, publish and verify package integrity hashes or signed provenance attestations. 5. Prefer a lockfile-backed local development dependency for reproducible automated installation rather than resolving the latest package at runtime. 6. Avoid global and non-interactive installation options unless they are necessary. Explain their effects and provide a lower-impact local installation command as the default. 7. Recommend inspecting the resolved package metadata before first use, particularly in CI or privileged environments. 8. Do not instruct users to run the installation command with `sudo` or an administrator account. ]]>
