POST: The unknown-unknown package dependencies

Open
#4 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
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
java, python

Research direction

The issue names no file, test, or entry point. Start by defining the intended post and its scope around shaded Java JARs, bundled Python binaries, and borrowed code; done means an agreed, actionable treatment of the dependency problem and its scalable mitigation.

Written by the indexing model from the issue text.

Description

blog

Shaded JARs in maven, bundled binaries in Python packages, borrowed code are unknown-unknown package dependencies (actually not really dependencies, since they are bundled).
Let's look at the problem and how help solve the mess at scale.

Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.