Privacyboard

Vendors

Code monitoring with GitHub

Connect GitHub so that a new SDK in your dependencies is proposed as a vendor on your Overview, the day it is pushed.

Updated 17 November 20263 min read

Your website shows the tools that run in the browser. Many of your subprocessors never appear there: payments, email sending, AI models, databases and error tracking run on your servers. Code monitoring reads the dependencies of your code, so a new SDK becomes a vendor proposal the day it is pushed. It is part of the Pro and Business plans.

#Connect GitHub

Open Settings → Integrations → Code monitoring (or Watch code at the top of Vendors) and choose Connect GitHub. GitHub asks which account and which repositories the Privacyboard app may read; pick only the repositories of your product. GitHub then asks you to authorize Privacyboard: this only lets Privacyboard check that the installation is yours, so nobody can attach someone else's repositories to their workspace. Editors, admins and the owner can connect it; only an admin or the owner can disconnect it.

Privacyboard reads the repositories a first time right away. After that, it reads them again each time a push to the default branch changes a dependency file. Check now reads them again on demand.

#What is read, and what is kept

The app asks GitHub for read-only access to the contents of the repositories you pick. Of those, Privacyboard reads only the dependency files on the default branch:

EcosystemFiles
JavaScript and TypeScriptpackage.json (dependencies, not devDependencies)
Pythonrequirements.txt, pyproject.toml
RubyGemfile (outside the development and test groups)
Gogo.mod (direct dependencies)
PHPcomposer.json

Folders such as node_modules, vendor, examples and tests are skipped. Only the names of the vendors these files point to are kept, with the package that showed each one, the repository it is in and, once it leaves the code, when it was last found (for 180 days). No code, no file and no GitHub token is stored: the access token GitHub gives the app lasts one hour and is used once.

Development tools are left out on purpose: a test runner or a linter is not a subprocessor.

#What you see

When a dependency points to a vendor that is not in your list yet, the Overview shows it under New: "New in your code: Stripe", with the vendor record from our catalog, the activities it would be tied to and the documents to validate again. Nothing changes until you apply it. Not a vendor keeps it out for good.

In Vendors, a vendor found in your dependencies carries an In your code label, with the package and the repository. The Monitoring line of the Overview's New list counts the repositories checked.

When an SDK leaves your dependencies, its vendor is proposed for removal: "No longer in your code: Stripe", with the activities that lose it and the documents that change. It is not proposed while another connected repository still uses it, or while the browser check still sees it on your website. Still used keeps it in your list until the code adds it and drops it again.

Code monitoring recognises the SDKs of about 80 common vendors (payments, analytics, error tracking, email, AI, hosting, authentication…). A package it does not recognise is not proposed: add the vendor yourself from Vendors → Add vendor.

#Disconnect

Disconnect in Settings deletes what code monitoring found in this workspace. To remove the app from your repositories as well, uninstall it from your GitHub settings (Settings → Applications on your account or organisation). If you uninstall it on GitHub first, Privacyboard forgets the connection by itself.

#FAQ

#Can Privacyboard change my code?

No. The app has read-only access, and Privacyboard reads only dependency files.

#Does it work with GitLab or Bitbucket?

Not yet. Your AI assistant can still read any repository and add what it finds, through the connector.

#GitHub says the installation could not be confirmed

Privacyboard connects an installation only when GitHub confirms that the person connecting can reach it. Connect GitHub again from Settings → Integrations → Code monitoring and authorize Privacyboard when GitHub asks; if someone else in your organisation installed the app, ask them to connect it, or to give you access to the installation on GitHub.

#Why is a vendor I use not proposed?

Either it is already in your vendor list, you marked it as not a vendor, it is a development dependency, or its package is not in our list yet. Tell us at hello@privacyboard.io and we add it.

Privacyboard is a guidance tool, not legal advice. This page describes what the product does today. Found something unclear or out of date? Write to hello@privacyboard.io.