Mark/osint-hub
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

No module blocking/availability tracking - blocked modules not configurable #19

New issue
Closed
opened 2026-04-03 19:00:44 +00:00 by Mark · 1 comment
Mark commented 2026-04-03 19:00:44 +00:00
Owner
Copy link

Problem

There's no system for:

  1. Tracking which modules are blocked (require API keys that aren't configured)
  2. Tracking which modules are available (have required configuration)
  3. Configuring module availability per investigation
  4. Dynamic module selection based on availability

Currently orchestrator hardcodes:

disallowed = set()  # Allow all modules including playbooks
allowed_modules = [m for m in sorted(ModuleRegistry._modules.keys()) if m not in disallowed]

But many modules require API keys that may not be configured:

  • virustotal requires VIRUSTOTAL_API_KEY
  • shodan requires SHODAN_API_KEY
  • etc.

Files

  • backend/app/services/investigations/orchestrator.py:268
  • backend/app/modules/base.py - EvidenceModule.requires_config field

Solution Required

  1. Check module requirements at investigation start
  2. Mark modules as "blocked" if required config missing
  3. Exclude blocked modules from allowed_modules
  4. Store blocked module list in InvestigationRun.config_json
  5. Allow user to configure blocked modules per investigation
  6. LLM should know which modules are available vs blocked
## Problem There's no system for: 1. Tracking which modules are blocked (require API keys that aren't configured) 2. Tracking which modules are available (have required configuration) 3. Configuring module availability per investigation 4. Dynamic module selection based on availability Currently orchestrator hardcodes: ```python disallowed = set() # Allow all modules including playbooks allowed_modules = [m for m in sorted(ModuleRegistry._modules.keys()) if m not in disallowed] ``` But many modules require API keys that may not be configured: - virustotal requires VIRUSTOTAL_API_KEY - shodan requires SHODAN_API_KEY - etc. ## Files - `backend/app/services/investigations/orchestrator.py:268` - `backend/app/modules/base.py` - EvidenceModule.requires_config field ## Solution Required 1. Check module requirements at investigation start 2. Mark modules as "blocked" if required config missing 3. Exclude blocked modules from allowed_modules 4. Store blocked module list in InvestigationRun.config_json 5. Allow user to configure blocked modules per investigation 6. LLM should know which modules are available vs blocked
Mark commented 2026-05-28 00:31:53 +00:00
Author
Owner
Copy link

This issue has been decomposed into the following sub-issues:

# Title Phase Scope
#76 No module blocking/availability tracking - blocked modules n There's no system for: 1. Tracking which modules are blocked (require API keys t
#77 No module blocking/availability tracking - blocked modules n - backend/app/services/investigations/orchestrator.py:268 - `backend/app/modul
#78 No module blocking/availability tracking - blocked modules n 1. Check module requirements at investigation start 2. Mark modules as "blocked"

Each sub-issue has been labeled with needs-triage and will be evaluated by the triage pipeline before queue routing.

This issue has been decomposed into the following sub-issues: | # | Title | Phase Scope | |---|-------|-------------| | #76 | No module blocking/availability tracking - blocked modules n | There's no system for: 1. Tracking which modules are blocked (require API keys t | | #77 | No module blocking/availability tracking - blocked modules n | - `backend/app/services/investigations/orchestrator.py:268` - `backend/app/modul | | #78 | No module blocking/availability tracking - blocked modules n | 1. Check module requirements at investigation start 2. Mark modules as "blocked" | Each sub-issue has been labeled with `needs-triage` and will be evaluated by the triage pipeline before queue routing.
Mark closed this issue 2026-05-28 00:31:53 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
agentic-osint

Agentic OSINT features

  
audit

   
blocked:commit-ready-failed

   
blocked:gate-fetch

   
blocked:gate-fetch

   
blocked:gate-lint

   
blocked:gate-plan

   
blocked:gate-research

   
blocked:needs-decision

   
blocked:needs-human

   
blocked:no-changes

   
blocked:preflight

Repo has dirty lint; kilo-gsd preflight refuses to dispatch until lint-cleanup lands

  
blocked:verify-failed

   
bug

Something is not working

  
chore

Config/cleanup item

  
deferred

Deferred — will revisit later

  
enhancement

Enhancement request

  
feature-request

   
in-progress

   
lint-baseline

   
lint-cleanup

kilo-gsd preflight lint gate: repo has dirty ruff state, cleanup required before fixer dispatch

  
needs-decompose

Issue needs decompose processing

  
needs-triage

   
performance

   
quickfix

   
security/medium

Medium severity security issue

  
triage-approved

Approved by triage

No labels
agentic-osint
audit
blocked:commit-ready-failed
blocked:gate-fetch
blocked:gate-fetch
blocked:gate-lint
blocked:gate-plan
blocked:gate-research
blocked:needs-decision
blocked:needs-human
blocked:no-changes
blocked:preflight
blocked:verify-failed
bug
chore
deferred
enhancement
feature-request
in-progress
lint-baseline
lint-cleanup
needs-decompose
needs-triage
performance
quickfix
security/medium
triage-approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Mark/osint-hub#19
No description provided.