Have inspectors explicitly declare dependencies on other inspectors
Metadata
Current evaluation
Feature request to make inspector dependencies explicit and auto-order them, preventing fragile manual ordering in insList. Untriaged, no maintainer response in 390 days.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and no activity for 390 days. It describes a legitimate architectural improvement (explicit dependency declarations for inspectors) but has not been assessed or prioritized by maintainers. Without maintainer engagement or evidence that this has been addressed elsewhere, it requires triage before any action can be taken.
Impact:
45
Quick Win:
20.25
Staleness:
85
Complexity:
55
Confidence:
40
Support Request:
10
Issue body
### What needs to get done
- Modify inspectors implementation and likely the `Inspector` interface to enable inspectors listing other inspectors they depend on.
- Rework `inspectors.New()` to dynamically order the inspectors based on their dependencies.
- Cleanup the error handling in inspectors dealing with potentially missing metadata from previous inspectors
### Why it needs to get done
Inspectors are run in the order they are declared in `insList` in `inspectors.New()`. Reordering this slice, or adding new inspector at the wrong position could have unintended and hard to diagnose behavior.
Moreover existing dependency between inspectors is implicit and could change on a minor code change.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
45
Quick Win:
20.25
Staleness:
85
Complexity:
55
Confidence:
40
Support Request:
10
|
needs triage | Feature request to make inspector dependencies explicit and auto-order them, preventing fragile manual ordering in insList. Untriaged, no maintainer response in 390 days. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.