mirror of
https://github.com/fleetdm/fleet
synced 2026-05-24 09:28:54 +00:00
7458100167
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #31605 I manually scanned our inlined dependencies for vulnerabilities and did not find any relevant ones. I added a dummy directory pointing at the source of our inlined dependencies so that automated vuln scanning tools can scan them. I did not include Kolide since the code was heavily adapted and only included a few tables. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Established infrastructure for automated vulnerability scanning of inlined third-party dependencies in Go and JavaScript environments, with comprehensive documentation and configuration to enable scanning via standard tools. * **Chores** * Updated gitignore configuration to refine dependency file tracking across the project. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub> <!-- end of auto-generated comment: release notes by coderabbit.ai -->
20 lines
527 B
JSON
20 lines
527 B
JSON
{
|
|
"name": "fleet-inlined-deps-vuln-check",
|
|
"version": "1.0.0",
|
|
"private": true,
|
|
"description": "Dummy package for automated vulnerability scanning of inlined frontend dependencies. This package is NOT used in Fleet builds.",
|
|
"license": "MIT",
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/fleetdm/fleet.git",
|
|
"directory": "third_party/vuln-check"
|
|
},
|
|
"dependencies": {
|
|
"node-sql-parser": "5.3.13"
|
|
},
|
|
"devDependencies": {},
|
|
"scripts": {},
|
|
"engines": {
|
|
"node": ">=18"
|
|
}
|
|
}
|