You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is building a generic module that can ingest a node named Dependency during Github ingestion to surface (at least) direct dependencies.
This would be useful for software composition analysis to identify supply chain risks in any ecosystem supported by Github.
Title: Ingest dependencies information as
Dependency
nodes using GH GraphQL APIDescription:
Currently, there is custom code to capture PythonLibrary dependencies https://github.com/lyft/cartography/blob/master/cartography/intel/github/repos.py#L523.
This is not generic (only supports Python setup.cfg and requirements.txt files), not covering other ecosystem's dependencies.
If the dependency graph is enabled (see https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph), Github automatically parses the project dependency lock files to generate a comprehensive graph.
This information is available via Github's GraphQL API, like:
The idea is building a generic module that can ingest a node named
Dependency
during Github ingestion to surface (at least) direct dependencies.This would be useful for software composition analysis to identify supply chain risks in any ecosystem supported by Github.
[optional Relevant Links:]
https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security
https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph
The text was updated successfully, but these errors were encountered: