FAQ: Does ScanCode work completely offline?

Open
#59 1 comment 0 reactions 0 assignees View on GitHub

@saurabh24thakur is already working on this.

Since Dec 25, 2025.

  • #101 by @Sahil-u07 — closed without merging

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
markdown
Domain
documentation

Research direction

Start by locating the relevant FAQ content in the Docusaurus/Markdown website repository. Use the issue's short and long answers to make the offline behavior and network-dependent integrations explicit, then verify the rendered page contains the clarification and caveats.

Written by the indexing model from the issue text.

Description

Question:

re: https://aboutcode.org/scancode/

Please consider adding a bullet point that states whether ScanCode requires network access.
That is, does it work completely offline or does it have to send signatures/source code to a third-party system?
We cannot run any tools on our code base without assurance that the code will remain on-prem.
I suspect ScanCode runs completely offline, but it would be great to have that clearly and explicitly stated somewhere

Short answer: Yes

ScanCode does not "phone home", works completely offline and does NOT send signatures/source code to a third-party system.

Long answer:

If you want to use VulnerableCode, PurlDB and MatchCode features with ScanCode.io or DejaCode, you will need to install these locally and configure them accordingly or else these will not work.

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.