Skip to content

Use case: supply chain history (what did we know when we shipped?) #27

Closed

Description

@adityamukho

Summary

Add a use case: Minigraf as a history store for each release's dependency tree, plus vulnerability and license data as it arrives.

The idea

Store every release's full dependency tree as facts. Add advisories (CVEs) and license findings as they are published. The two time axes map cleanly:

  • Valid time: when a release contained a given package version.
  • Transaction time: when you learned something about that package (an advisory, a license change).

The advisory almost always arrives after the release. That gap is the point.

Questions it answers

  • Which releases shipped with this library version, directly or transitively?
  • When that release shipped, did we already know the version was vulnerable?
  • How long did each affected release stay in use after the advisory was known?

Why Minigraf fits

  • Transitive dependencies are a recursive rule.
  • "What we knew at ship time" is an :as-of query on transaction time. "What was actually in the release" is a valid-time query. Most tools keep only one of these.
  • One file per product or repo fits the one-file-per-unit model.

Suggested content

  • The idea and the time-axis mapping
  • A small fact schema (release, package, version, depends-on, advisory, affects)
  • A recursive rule for transitive dependencies
  • One query contrasting "known at ship time" with "true at ship time"
  • Possible inputs: SBOM files (CycloneDX, SPDX), lockfiles, OSV advisories

Notes


Generated by Claude Code

Activity

  1. adityamukho commented on Oct 19, 2026

    @adityamukho
    ContributorAuthor

    Builds on the git sidecar idea in #34, which provides the commit and entity index this use case attaches facts to.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions