InQuest / InQuest/ThreatKB

Add YARA signature generation capability

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

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
104
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reviewing the linked yara-signator project and ThreatKB's existing YARA-rule workflow. Determine where signature generation belongs and define the expected inputs, outputs, and integration boundary before implementing the capability. Done means ThreatKB can generate YARA signatures through a documented, testable workflow.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.