-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
guide
Aiming to be a fully transparent company. All information about source{d} and what it's like to work here. (by src-d)
-
semgrep
Lightweight static analysis for many languages. Find bug variants with patterns that look like source code.
I've been playing with some ideas for creating a SQLite database of classes, functions and suchlike found in Python code, so I can analyze my codebases with SQL queries.
I've had some good initial results with https://github.com/davidhalter/jedi - which is the Python introspection library that powers various editor autocomplete implementations. I have a prototype which uses that to create a SQL database of functions, classes and places that they are used.
I've also been playing with https://github.com/github/semantic - it can parse Python, JavaScript and other languages and offers a --json-symbols option which dumps out a JSON object showing the symbols (functions, variables etc) found in the code.
Just because you find it readable does not mean others can; also, color contrast is not the only thing that affects readability. In this case, the issue is font weight.
Here's some discussion on the issue: https://github.com/w3c/wcag/issues/665
Good piece, tho not new ideas. Ton of references, two recent that immediately come to mind
https://github.com/src-d/guide
I'm with you on this one. I'd actually suggest https://github.com/CoatiSoftware/Sourcetrail could be extended to do this, though I haven't found the time yet. For example https://github.com/CoatiSoftware/SourcetrailPythonIndexer and under the hood the file format is SQLite: https://github.com/CoatiSoftware/SourcetrailDB
At r2c, we've been using our own https://semgrep.dev/ to search across our repositories and take inventory of certain things. For instance, we have a Semgrep rule that finds and extracts API routes and whether they require authentication.
See page 27 for a visualization (PDF warning): https://owasp.org/www-chapter-dorset/assets/presentations/20...