T08 · Insecure Dependencies
- Location
references/wave-planning.md:30- Finding
Unpinned Third-Party JavaScript Loaded from an External CDN
- Content
View full analysis
- Remediation
View remediation
/dist/chart.umd.min.js" integrity="sha384-" crossorigin="anonymous"> ``` 2. Obtain the integrity hash from a trusted source or generate and verify it against the reviewed artifact. Update the pinned version and hash only through a controlled dependency-review process. 3. Prefer vendoring the audited JavaScript asset in the project and serving it locally when deployment and licensing requirements permit. 4. Configure a restrictive Content Security Policy that limits script sources to explicitly approved origins and avoids `unsafe-inline` and `unsafe-eval`. 5. Add automated checks that reject versionless CDN package URLs and external scripts without integrity metadata. 6. Update the agent prompt template so all spawned agents receive the secure, version-pinned dependency requirement and do not recreate the unsafe pattern. ]]>
