Design end-to-end process with decentralized scanning using the AboutCode stack

Open
#140 2 comments 0 reactions 0 assignees View on GitHub

@dheeraj1174 is already working on this.

Since Dec 22, 2025.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

No source files, tests, or entry points are named. Start by reviewing the Mermaid sequence diagram and the described flow between frontend-scancode.io, scan-storage, DejaCode, PurlDB, and backend-scancode.io; done means an agreed end-to-end decentralized scanning and data-federation process.

Written by the indexing model from the issue text.

Description

Short Description

This is a process where software team run decentralized scans and federate their data in a centralized DejaCode and PurlDB

Possible Solution/Implementation Details

Screenshot 2024-06-10 at 18-45-15 Online FlowChart   Diagrams Editor - Mermaid Live Editor

sequenceDiagram
    codebase->>+frontend-scancode.io: Run front-end scan
    frontend-scancode.io->>+scan-storage: Send inventory JSON to some storage
    scan-storage->>+DejaCode: Load inventory JSON in new DejaCode product version 
    DejaCode->>+PurlDB: Collect on-demand the package in PurlDB
    PurlDB->>+backend-scancode.io: Run full scan on packages
    PurlDB->>-DejaCode: Get scan from purldb

See https://mermaid.live/edit#pako:eNptkctOwzAQRX9l5C0NH-BFFzQSEkIUkW02k3haAvY4-FFUVf13xjURCJqVk3vu8cQ-qdEbUlpF-sjEI7UT7gO6nkGekg0YqVmvb3bBcyI2TRyRS3A7eQ0vmeGSNBJBiWrzGl0s5bWJyQfck4aulCY-EMuXIzx02ydIHqJ3BN9Q1f2uFU1Lb7gRq4ZHj_8UEwPTJywQzMGbPCY4UIiTZ6jOJS6-5xxse6dh460lIT03hhzKdOlV-ji-y8bFW8EqqOtSHwS4fjTZ2svwYlw08U-7-fmZe0qVluNzMAthhp7VSjkKDicj93Qq7V7JWI56pWVpaIfZpl71fBYUc_LdkUelU8i0Unk2mJZrVXqHNtL5C5HyrDI

Dominant language
Batchfile
Stars
316
Forks
257
PR merge metrics
No merged PRs in 30d

Getting set up

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/aboutcode

All issues in aboutcode-org/aboutcode

Similar issues

More Data Engineering issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.