[FEATURE] AI 비의존 API 추가 - #43
Merged
Merged
Conversation
minsoo0506
force-pushed
the
feat/#42-no-ai
branch
from
June 25, 2026 11:38
e415c90 to
8c5674e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
요약
AI를 사용하지 않고 기존 신호 기반으로 분석 결과와 판정 사유 summary를 생성하는 no-AI 분석 API를 추가했습니다.
POST /api/v1/analyze/no-ai/sync추가ai_request_failed,ai_parse_error,ai_disabled등으로 구분OpenPhish 최신 악성 URL 100건으로 AI 사용 API와 no-AI API를 비교했습니다.
결과적으로 AI 사용 API가 no-AI API보다 탐지율이 30.67%p 높았습니다.
특히 no-AI API는
EXTERNAL_LINK_OVERUSE,SPA_SHELL,PII_COLLECTION_FORM,LOGO_ALT_IMPERSONATION,NEW_DOMAIN,NO_HTTPS,BRAND_IN_URL같은 약한 신호 조합만 잡힌 경우 악성 판단 임계값에 도달하지 못하는 케이스가 많았습니다.답변 내용도 차이가 있었습니다.
따라서 사용자에게 제공하는 최종 판정 이유는 AI를 사용하는 것이 적절해 보입니다. 다만 AI 장애나 API 비용 제한 상황을 대비해 no-AI summary는 fallback 경로로 유지하는 것이 좋을 것 같습니다.
연관 이슈 및 Close 할 이슈
close #42
Pull Request 체크리스트
TODO