Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why we tied all the examples with graph database? #4

Open
nashid opened this issue May 28, 2021 · 1 comment
Open

why we tied all the examples with graph database? #4

nashid opened this issue May 28, 2021 · 1 comment

Comments

@nashid
Copy link

nashid commented May 28, 2021

I see all the examples are tied with the graph database.

From my first look, it appears plume has two use-case:

(a) It augments joern and adds support for Java
(b) It can interface with different graph databases

So I think providing examples for both these use cases would be useful.

However, it looks like without initializing the driver, I cant even parse a java class. My intention is to use Plume as a program analysis tool.

Am I missing something?

@DavidBakerEffendi
Copy link
Contributor

Super late reply this must've slipped past me. But I have re-written Plume to tie in closer to the Joern/CPG world by implementing everything in Scala. The OverflowDB example now includes a reachability call one can use for taint analysis and this wraps around CPGQL's reachableBy and aims to save results between analysis (eventually).

Everything in Plume is backed by some "database" whether it's an intermediary in-memory representation or long term database backend. Often small DiffGraph OverflowDB objects are used when dealing with changes to be persisted later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants