HASecuritySolutions/VulnWhisperer

in addition to scan results, store and ship scan metadata about scans

Open

#7 opened on Nov 27, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (1,320 stars) (281 forks)batch import
enhancementhelp wanted

Description

Use to track when scans are running, supposed to run, and latest results. This should be a separate scan index.

It should include all the data about a scan result, without the history information. Including:

status, control, uuid, name, read, enabled, owner, creation_date, user_permissions, folder_id, starttime, timezone, last_modification_date, shared, type, id, rrules)

Contributor guide

Tech stack
python
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
PythonVulnWhisperer project understandingdatabase concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current implementation of scan result storage (likely in models or storage layer) to understand how results are indexed and stored. Then design a separate index for scan metadata as described, including all listed fields. Look for any existing related code or discussion in the comments. Since this issue is from 2017, verify the current codebase structure and adapt accordingly. Discuss with maintainers if needed.