Design end-to-end process with decentralized scanning using the AboutCode stack
@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
- Domain
- data, distributed-systems
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
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
- Dominant language
- Batchfile
- Stars
- 316
- Forks
- 257
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aboutcode-org/aboutcode
-
Cross-reference OpenChain CRA Compliance ChecklistMay be free again @PaulitePavitra claimed this 41 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aboutcode-org/aboutcode#309 · 6 comments ·
-
scancode-next: Plan federated software supply chain data infrastructurePossibly taken @ziadhany claimed this 6 days ago. Openmaintainers-only
Difficulty 4/5 3-5 days Newbie friendliness 45/100
aboutcode-org/aboutcode#325 · 2 comments · 2 assignees ·
-
scancode-next: Improve documentation, review documentation issues and pull requestsPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
aboutcode-org/aboutcode#324 · 1 assignee ·
-
scancode-next: Gather requirements through interviews with key usersPossibly taken @hesa claimed this 8 days ago. Openmaintainers-only
Difficulty 5/5 Over a week Newbie friendliness 25/100
aboutcode-org/aboutcode#323 · 1 assignee ·
-
scancode-next: Prepare ScanCode and AboutCode workshopsPossibly taken @adaaaam claimed this 6 days ago. Openmaintainers-only
aboutcode-org/aboutcode#322 · 1 assignee ·
All issues in aboutcode-org/aboutcode
Similar issues
-
author-page correction move-papers
Difficulty 1/5 Under an hour Newbie friendliness 78/100
acl-org/acl-anthology#10978 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Missing ToCsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
davwheat/rail-announcements#395 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
soroswap/token-list#125 ·
Maintainers usually reply within 1 day
-
module/data.csv Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ballerina-platform/ballerina-library#9792 ·
Maintainers usually reply within 1 day