Threat detection

Open
#66 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
security

Research direction

No files, tests, or entry points are named. Start by reviewing the extension's current implementation and how it handles logs and databases, then clarify which suspicious usage patterns and abuse techniques are in scope. Done requires an agreed detection scope and a way to validate the findings.

Written by the indexing model from the issue text.

Description

Proactive threat detection

  • Identify suspicious usage patterns by examining logs, databases, etc.
  • Be aware of new abuse patterns and exploitation techniques that are relevant to the application (based on context and knowledge)
Dominant language
TypeScript
Stars
793
Forks
60
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gemini-cli-extensions/security

All issues in gemini-cli-extensions/security

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.