proditis/orunmila

a simple tool to refine and produce lists for your bugbounty and pen-test engagements

orunmila's Issues

Split operations into multiple files to ease development and avoid conflicts in merge

Improve Github Pages content for the project

Improve Github Pages content by editing the README.md in the gh-pages branch

Make sure your Pull Request is targeting the correct branch gh-pages and NOT the default one main.
Dont forget to mention the issue by adding something like the following into your message issue #25

Introduce test cases

Todo list

These are some of the initial things we want to do for the project.

• Use methods to simplify some operations and avoid passing certain values as arguments https://gobyexample.com/methods
• Update usage and readme to include that the application and subcommands also support -help
• add exclude tags filtering (ie -tags a,b,c -etags d will list words from a,b,c tags and that dont have d tag)
• Check if we can add loading database to memory to speed things up
• Add support for case sensitive words if needed (this involves using collate nocase on the schema and our search)
• Add support to search for -words as well as -tags
• Make operations into subcommands
  • list,ls: display entries from -tags or -words
  • delete, rm: delete either -tags list or -words list. When both are given then only their explicit relation from wt table will be deleted.
• #28
• help: Details usage of all operations
• import: imports a file into the database
• search: searches the database for the given tags
• add: add entries to the database from the cli
• vacuum: pack the database to save space
• Fix the tags logic for search its broken right now. If tags where given but not found then WE MUST NOT return results.
• #18
• #16
• use log.* functions instead of fmt.println where appropriate.
• only open the database for write when we do imports. in any other case ?mode=readonly
• Make a proper module structure and ensure the dependencies get installed from go.mod
• Add Github workflow to build binary releases
• Make sure the database files are created into the current working directory and not wherever the binary is installed
• Make the -db flag only on main()

On search without tags simply list the database words

• On search without tags simply list the database words entries
• On search with tags but none are found, do nothing.

Add `-st` (for show-tags) support on searchSubcmd which will include the a comma separated list of the tags of each entry eg `word1 => tag1,tag2,tag3`

fix usage bug with default database, it gets displayed two times

fix usage bug with default database, it gets displayed two times