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.

Sign up for GitHub

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

Jump to bottom

Ingest GitHub data #228

Closed
tayasteere opened this issue Jan 16, 2020 · 2 comments
Closed

Ingest GitHub data #228

tayasteere opened this issue Jan 16, 2020 · 2 comments

Comments

@tayasteere
Copy link
Contributor

Title: Ingest GitHub repo data

Description:
Ingest GitHub repo info to enable exploration of user access to code. This is currently a Lyft internal module.
@tayasteere tayasteere added enhancement WIP work in progress keep fresh Disables stalebot from closing an issue labels Jan 16, 2020
@nealharris
Copy link

It seems like this could enable more than just understanding user access to code. For example, suppose GitHub detects a vulnerable dependency in a manifest file for some app. GitHub can tell you when that vulnerability has been patched in your source control, but won't tell you whether that fix has been deployed everywhere.

Maybe that's scope creep for this issue? Anyway, I've always thought it'd be cool to connect vulnerable dependency data with a tool that understands where that code is deployed.

achantavy pushed a commit that referenced this issue Feb 13, 2020
@tayasteere
Add ability to ingest GitHub repository information (Issue #228) (#229)
cd1870e 
* Added parsing for extension permissions to crxcavator ingest

* Updated documentation for crxcavator ingest

* removed debugging statement

* Updated docs to address comments
Fixed missing fields

* Fixed cypher error

* Changed index and import to reference ChromeExtensionPermissions id

* Remove potentially bad import data

* removed unnecessary json.dumps call

* Added back dumps to get information on unknown field for logging, not ingesting though

* Added tagging for all logging calls

* clarified code comment

* lint fix

* crxcavator crash fix before merge from master

* Initial github commit

* Initial github commit

* Moved Github setup to config object
Added documentation for configuration of Github ingest to README.md

* address comment on using templating

* Changed repo owner relationship to entity-owner->repo
Added default for unconfigured Github handling
@achantavy
Copy link
Contributor

@nealharris This is exactly the way that we use this data internally :). In the past we wrote these functions without thinking about OSS but now we're writing as much as we can in open-source-land first. Definitely welcome help here too if there's a particular app you have in mind!

@achantavy achantavy removed WIP work in progress in-testing keep fresh Disables stalebot from closing an issue labels Feb 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nealharris @tayasteere @achantavy