Navigation Graph #19
Closed
Navigation Graph #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Added non-headless content parsers based on security-crawl-project * Added output + misc options + cli beginning * Started runner creation + misc additions to parsers * Added scope manager * Added extension based validators * Added initial CLI implementation + misc * Misc improvements * Fixed a crash due to nil response * Misc fixes to output * Added banner + misc * Misc fixes + added version + misc * Misc fixes * misc
Mzack9999
added
Status: In Progress
Adding GitHub Actions
Mzack9999
removed
the
Status: In Progress
|
Blocked: needs rebase with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR implements an extensible prototype navigation graph interface with two implementations:
The shortest path calculation is performed using Dijkstra's algorithm for a directed graph with unitary edge cost.
The implementation was done on the standard library engine and should be extended later for headless navigation, differentiating edges based on navigation actions/connection types
How to modify the implementation
projectdiscovery/katana/ent/schema/endpoint.gogo generate ./ent