Chrome Extension

Latest Audit Result

Audited exa-labs/Exa-highlight-extension, the accessible repo matching the requested exa-labs/exa-highlight slug. The integration is API-direct with no SDK dependency and calls only POST /search through api/search.js to https://api.exa.ai/search; it does not call /contents, /findSimilar, or /answer. The /search request uses type: "instant", which is valid in current Exa docs and appropriate for low-latency extension UX, but mismatches the declared auto capability. The request only asks for contents.highlights, so declared text content is still not implemented. The highlights request still uses deprecated numSentences and highlightsPerUrl fields; the Feb 2026 changelog says to migrate to maxCharacters or highlights: true, and highlightsPerUrl is accepted but ignored. No sunset endpoints or April 2026 deprecation fields are used. Build validation could not run because this repo has no package.json, so npm run build is not available.

Missing Features (7)

• DEPRECATED: /search still sends contents.highlights.numSentences, deprecated by the Feb 2026 Exa changelog in favor of maxCharacters or highlights: true.
• DEPRECATED: /search still sends contents.highlights.highlightsPerUrl, deprecated by the Feb 2026 Exa changelog; current docs say it is accepted but ignored and should be removed.
• Declared content option text is not implemented: the only /search request sends contents.highlights and never sends contents.text.
• Declared search type auto does not match the implementation: the only /search request hardcodes type: "instant". Instant is valid, but the capability declaration is inaccurate unless the code is changed to auto.
• Replace contents.highlights: { query, numSentences: 3, highlightsPerUrl: 2 } with either contents.highlights: true for the safest default, or contents.highlights: { query, maxCharacters: N } when a fixed highlight budget is required.
• Align the declared search type capability with implementation by changing the declaration to instant, or change the request type to auto if the integration should prioritize default balanced relevance over lowest latency.
• If text remains a declared capability, add contents.text (boolean or object with maxCharacters) to the /search request; otherwise remove text from the declared capabilities.