Create a dataset of historical PRs

Open
#33 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
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
data, security

Research direction

No files, tests, or entry points are named. Start by reviewing the repository's security-extension purpose and the three requested categories; done means a historical PR dataset covering noteworthy false positives, true positives, and borderline true positives lacking project context.

Written by the indexing model from the issue text.

Description

  • Noteworthy false positives
  • Noteworthy true positives
  • Borderline cases that are technically true positives, but lack project context i.e. don't understand the feature, requirements or threat model
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.