T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Third-Party npm Package Installed Globally
- Content
View full analysis
- Remediation
View remediation
``` 2. Record and verify package provenance, including the expected npm registry, package publisher, source repository, release signature, and integrity digest. 3. Include a lockfile or equivalent integrity-controlled installation manifest where the Skill platform supports it. 4. Prefer a project-local or isolated installation over a global installation so the executable does not affect unrelated projects or sessions. 5. Audit the package source, npm lifecycle scripts, and transitive dependencies before allowing automated installation or execution. 6. Disable lifecycle scripts during installation when they are not required: ```bash npm install --global --ignore-scripts openfun-cli@ ``` If lifecycle scripts are required, review and explicitly approve them instead. 7. Run the CLI in a sandbox or restricted account with access only to the directories and network destinations required for video generation. 8. Ensure `~/.openfun/config.json` is created with owner-only permissions, avoid exposing it in logs or backups, and provide a documented token-revocation procedure. 9. Revalidate package integrity and security before updating the pinned version. ]]>
