Make sure all 3P direct and transient dependencies are signed

Open
#401 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system, security

Research direction

Start by reviewing the repository's Java dependency declarations and build pipeline configuration. Determine how direct and transitive dependencies can be verified as signed, and how produced packages are signed. Done means the pipeline signs every provided package and rejects any dependency chain containing an unsigned package.

Written by the indexing model from the issue text.

Description

All packages we provide to other teams:
a. Are signed by our build pipeline.
b. Do not take a dependency (directly or indirectly) on any package which is not signed

Dominant language
Java
Stars
46
Forks
49
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/azure-kusto-java

All issues in Azure/azure-kusto-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.