Supply Chain
Track direct and transitive dependencies, versions, and drift across repositories.
OpenHack inventories the software packages used by your repositories and shows how direct and transitive dependencies are connected. Teams can see which versions are in use and where different repositories have drifted apart.
The dependency context supports software composition analysis and gives security and engineering teams a shared view of components that need review or an update.
How it works
- 01
Read dependency sources
Inspect the package manifests and lockfiles in each connected repository.
- 02
Build the dependency graph
Resolve direct packages and the transitive components they introduce into the application.
- 03
Compare repositories
Identify the versions in use and show where services or repositories have diverged.
- 04
Surface components for review
Connect dependency location and version context to software composition analysis findings and update work.
What it covers
Direct dependencies
List the packages explicitly declared by each application or service and the versions selected by its lockfile.
Transitive dependencies
Show packages introduced indirectly through another dependency and the path that brought them into the project.
Version drift
Compare package versions across repositories so teams can find inconsistent or outdated components.
Multi-repository inventory
Maintain a consolidated view of dependencies across the repositories connected to the platform.
What you get
- A direct and transitive dependency inventory
- Package versions and repository locations
- Dependency paths and relationships
- Version drift and components requiring review
Get started
Connect repositories to the managed platform to build a dependency inventory and review package versions across your codebase.