Skip to content

RFC: Introduce "primary package" vs. "embedded- or sub-packages" #2418

Description

@pombredanne

Short Description

In the same way we have dependencies, we often have:

  • a package within a package such as a node_modules in an npm, mono-repos, uberjars and fatjars, and similar
  • multiple personalities for the same package (bower and npm)

We should have a heuristic to report one of these has primary and the other as sub/embedded packages.
This would likely be done in a post-scan step.
Data-wise this could be a list of Package URL similar to what we have for dependencies.

Select Category

  • Enhancement

Activity

  1. pombredanne commented on Aug 20, 2021

    @pombredanne
    MemberAuthor

    A few thoughts on design:

    • when a package embeds other packages, we do not want to report the files of sub-pckages as being part of these of the main parent packages
    • we would want to introduce a new embedded_packages attribute that would list sub packages in the parent
  2. added this to the v31.0 milestone on Sep 24, 2021
  3. pombredanne commented on Apr 25, 2022

    @pombredanne
    MemberAuthor

    We do not have such concept yet and this requires further design.

  4. removed this from the v31.0 milestone on Apr 25, 2022
  5. pombredanne commented on Sep 2, 2023

    @pombredanne
    MemberAuthor
  6. armijnhemel commented on Sep 13, 2023

    @armijnhemel
    Collaborator
  7. pombredanne commented on Jun 17, 2024

    @pombredanne
    MemberAuthor
  8. added
    RFCRequest for comment, from the maintainers, users and the larger aboutcode community.
    on Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions