starbase
starbase copied to clipboard
Graph-based security analysis for everyone
## **Description** As a user I want to run Starbase using the @jupiterone/starbase:0.2.0 npm package. Attempting to use the Starbase yarn commands results in /starbase/bin/starbase requiring non existent /starbase/dist/src. ##...
# Description Currently we support uploading data collected by Starbase to Neo4j. It would be great if Starbase users could alternatively support JupiterOne as a storage target. This would allow...
This would add **dotenv** as a dev dependency, as a low-effort solution to import user-defined environment variables from **.env** e.g: .env ``` ENV_VARIABLE_VALUE=123 ``` config.yaml ``` ... someProperty: ${ENV_VARIABLE_VALUE} ```
I use https://github.com/netbox-community/netbox as a source of system/network related information. It contains much of the same data as your Host, IPAddress, Asset, etc models and I was looking to have...
It would be great if the CLI had a spinner for when work is being performed. The `setup` and `run` command take time and a spinner would make the CLI...
The `config.yaml` allows you to specify integrations to use and pull down. I think it would be cool to be able to specify specific version or branches of the integration...
Currently starbase only reads from `config.yaml`. It would be nice to have the option to point to another file to be used as the config. Example: `yarn setup -f anotherconfig.yaml`
This issue was seen when running`starbase setup` on WSL. The user was attempting to clone the repo into the windows filesystem which is mounted by the WSL `/mnt/c/....`. There appears...
Currently, Starbase only supports the `.yaml` file extension for `config.yaml`. We should also support `config.yml`.
When we are doing `yarn starbase run` to run the Google Cloud(graph-google-cloud) integration with Starbase, the .env in `.integrations/graph-google-cloud` is not generated correctly. Therefore nothing is imported into the Neo4J...