gtri / lowendinsight-get Goto Github PK

In this case, all 12 are cached - thus the duration of 0, but the risk_counts aren't correctly tallied when reports are pulled.

  "metadata": {
    "times": {
      "start_time": "2020-03-11T00:15:36.482550Z",
      "end_time": "2020-03-11T00:15:36.512132Z",
      "duration": 0
    },
    "risk_counts": {
      "": 12
    },
    "repo_count": 12

Add a config variable that allows LEI-G to start without Redis backend.

Currently no way to click back to the "front" landing page.

Need some basic analytics

https://lowendinsight.dev points to 192 in the /doc HTML. Maybe use template so that site references target URL?

...in mix.exs. Will require functionality to transform the mix deps.tree to a list of URLs. The hex API can be used, but will have to parse out the links attribute to get to it. Figure this is functionality that will exist in lei-get to keep the library "disconnected".

First step in dog-fooding.

Currently, we're hard-coded to support Elixir, but need to support n-languages, passed in as path argument.

e.g. lowendinsight.dev/gh_trending/[elixir|npm|pypi|etc.]

Fetch list every day from: https://github.com/dependabot/elixir-security-advisories

Analyze any new vuln libs and report to a static HTML page.

Builds broken until org exists in hub.docker.com

Each "scheduler" process is 7 bucks, and having a single scheduler makes the most sense. This is probably as simple as providing a helper to run the analysis for each language sequentially.

LEI needs to display the repo reports for each item in a languages' page, in an optimal UX experience.

DoD: when a "wireframed" design is delivered and accepted by the core LEI team.

Use this feed:
https://github.com/huchenme/github-trending-api

Schedule a run, "report" daily - make report available as HTML page.