Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion backend/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"dotenv": "^17.2.3",
"drizzle-orm": "^0.45.2",
"elysia": "^1.4.28",
"exa-js": "^1.0.11",
"exa-js": "^2.12.1",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lockfile not updated to match new major version

High Severity

The package.json declares "exa-js": "^2.12.1" but the bun.lock still declares "exa-js": "^1.0.11" in the workspace section and resolves to exa-js@1.10.2. This mismatch means bun install --frozen-lockfile (typical in CI) will fail, and any fresh install will pull v2.x which may break the application due to major version API changes without corresponding code updates.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e54f216. Configure here.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Major version bump may break undocumented extras option

Medium Severity

The getContents call in exa.ts passes extras: { imageLinks: 1 } which does not appear in any exa-js v2 documentation. When v2.12.1 is actually installed, this option may be silently ignored or rejected, resulting in image link data no longer being included in fetch-content responses — a silent loss of functionality with no error surfaced to callers.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit e54f216. Configure here.

"ipaddr.js": "^2.3.0",
"jose": "^6.2.2",
"openai": "^6.34.0",
Expand Down
Loading