T08 · Insecure Dependencies
- Location
README.md:27- Finding
Unpinned npm packages allow mutable third-party code execution
- Content
View full analysis
- Remediation
View remediation
``` 2. Avoid automatically suppressing installation confirmation with `-y` in agent-directed workflows. Require explicit user approval before downloading or executing a package. 3. Publish and document expected package integrity information, such as the npm distribution SHA-512 value, and verify it before execution in security-sensitive deployment environments. 4. Pin transitive dependencies in the externally installed runtime using a committed lockfile and reproducible release process. 5. Use npm provenance attestations, protected publishing with mandatory multi-factor authentication, and short-lived or trusted publishing credentials. 6. Separate package download from execution. Inspect the resolved version and package contents before invoking its binary. 7. Ensure the Skill checks and reports the installed runtime version rather than automatically upgrading to an unspecified latest release. 8. Audit the external `sysu-anything` runtime separately because it performs the authenticated campus and Apple operations that are outside this repository's source scope. ]]>
