Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] showSubtechniques in SVGConfig does not show the sub techniques in the SVG

Open
  • Is something wrong?
#169 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start in mitreattack.navlayers.exporters.to_svg, focusing on SVGConfig and ToSvg.to_svg. Reproduce the issue with showSubtechniques="all" and the supplied layer settings, then compare the generated SVG with the attack navigator output. Done means the SVG includes expanded subtechniques under the described configuration.

Written by the indexing model from the issue text.

Description

bug

Expected Behavior

Expanded sub techniques in SVG

Actual Behavior

SVG is not showing sub techniques, while the attack navigator does

Steps to Reproduce the Problem

  1. create a json with:
    layout: "expandedSubtechniques": "all"
    techniques "showSubtechniques": True
    "selectSubtechniquesWithParent": True
  2. Validate that the json contains:
    layout: "expandedSubtechniques": "all"
    techniques: "showSubtechniques": true
    "selectSubtechniquesWithParent": true
  3. Validate that the json works in attack explorer
  4. Import: from mitreattack.navlayers.exporters.to_svg import ToSvg, SVGConfig
  5. svgconf =SVGConfig(width=118.9, height=84.1, unit="cm", showHeader=False, fontSize=12, showSubtechniques="all")
  6. export with
    exporter = ToSvg(domain='enterprise', source='local', resource=resource_path, config=svgconf)
    exporter.to_svg(layerInit=layer, filepath="Coverage.svg")

Possible Solution

Review > mitreattack.navlayers.exporters.to_svg

Dominant language
HTML
Stars
744
Forks
175
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 mitre-attack/mitreattack-python

All issues in mitre-attack/mitreattack-python

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.