mandiant / mandiant/VM-Packages
Change name and add subcatagories for packages wiki into table of contents
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 246
- Forks
- 98
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 7
Description
### Details
1. Looking at the packages wiki we have added [here](https://github.com/mandiant/VM-Packages/wiki/Packages), it would be nice to have the name for the section not called **"Automatically generated"**, but rather something more useful, like **"Tools"**.
2. Additionally, I think it would be very useful to have the tool categories listed underneath that new category name so that people can see what high level categories exist at a glance.
3. In regards to "The packages in the [FLARE-VM default configuration](https://raw.githubusercontent.com/mandiant/flare-vm/main/config.xml) are marked in bold.", it is a bit difficult to see which tools are **bolded** due to each being a hyperlink. Maybe we should try to add a link to the package in a third column or find another means of doing this? I'm open to suggestions for this improvement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Packages wiki page and inspect how its table of contents and package links are generated; the issue does not identify a source file or generation entry point. Done means the section has a useful name, tool categories appear beneath it, and the FLARE-VM default packages are easier to distinguish from other links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100