Skip to content
Snippets Groups Projects
Select Git revision
  • renovate/major-opa
  • advisory/tj
  • main default protected
  • defect/telem
  • docs/pattern
  • spike/go-tools-124-gql
  • spike/go-tools-124
  • chore/deepmap
  • docs/mas
  • build/notify
  • fix/du
  • defect/diff
  • defect/json
  • chore/schema
  • feat/diff-json
  • chore/typo
  • build/binaries
  • build/changelog-
  • defect/otel
  • chore/otel
  • v0.116.2 protected
  • v0.116.1 protected
  • v0.116.0 protected
  • v0.115.3 protected
  • v0.115.2 protected
  • v0.115.1 protected
  • v0.115.0 protected
  • v0.114.0 protected
  • v0.113.5 protected
  • v0.113.4 protected
  • v0.113.3 protected
  • v0.113.2 protected
  • v0.113.1 protected
  • v0.113.0 protected
  • v0.112.0 protected
  • v0.111.1 protected
  • v0.111.0 protected
  • v0.110.2 protected
  • v0.110.1 protected
  • v0.110.0 protected
40 results

client.gen.go

  • Jamie Tanna's avatar
    0d842053
    feat: add ability to source data into `dependency_health` · 0d842053
    Jamie Tanna authored and Jamie Tanna's avatar Jamie Tanna committed
    As part of #260, we want to make it possible to discover more insights
    into our dependency tree, which allows us to make further analyses
    around how healthy the dependency may be.
    
    This introduces a new table, `dependency_health`, which contains fields
    of relevance, and will be expanded upon in the future.
    
    This also introduces the ability to sync the data, via Ecosyste.ms and
    OpenSSF Security Scorecards, using a new subcommand `dmd db generate
    dependency-health`.
    
    We can rely on Ecosyste.ms as the primary source of data, using pURL
    lookups to (hopefully) simplify the translation between package names.
    
    Ecosyste.ms exposes an OpenAPI spec we can auto-generate our client for,
    and as we only need a single operation in the API, we can use the new
    `include-operation-ids` configuration to tune the resulting output.
    
    Closes #260.
    0d842053
    History
    feat: add ability to source data into `dependency_health`
    Jamie Tanna authored and Jamie Tanna's avatar Jamie Tanna committed
    As part of #260, we want to make it possible to discover more insights
    into our dependency tree, which allows us to make further analyses
    around how healthy the dependency may be.
    
    This introduces a new table, `dependency_health`, which contains fields
    of relevance, and will be expanded upon in the future.
    
    This also introduces the ability to sync the data, via Ecosyste.ms and
    OpenSSF Security Scorecards, using a new subcommand `dmd db generate
    dependency-health`.
    
    We can rely on Ecosyste.ms as the primary source of data, using pURL
    lookups to (hopefully) simplify the translation between package names.
    
    Ecosyste.ms exposes an OpenAPI spec we can auto-generate our client for,
    and as we only need a single operation in the API, we can use the new
    `include-operation-ids` configuration to tune the resulting output.
    
    Closes #260.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
client.gen.go 14.12 KiB