BaudBound uses an Official blacklist to respond to reviewed security concerns involving a repository, publisher, domain, script, or exact package file.
The list comes from the BaudBound API at api.baudbound.app. The runner downloads only active public entries. It does not send your installed script list, package hashes, machine identity, or repository choices to the API.
The Official blacklist is different from your Personal block list.
| List | Controlled by | Purpose |
|---|---|---|
| Official blacklist | BaudBound maintainers | Apply reviewed security advisories and mandatory restrictions |
| Personal block list | You | Hide and disable a repository on one runner installation |
Official restrictions cannot be ignored in the runner. A personal block can be removed whenever you choose.
Every entry has one severity.
| Severity | What the runner does |
|---|---|
| Advisory | Shows the reason and advisory link without blocking the content |
| Restricted | Hides matching browser entries and blocks matching downloads, imports, approvals, installations, and updates |
| Quarantined | Applies the restricted behavior, disables matching installed scripts, removes their queued runs, and prevents new runs |
| Critical quarantine | Applies quarantine and requests cancellation of matching active runs |
Quarantine does not delete the package, approval history, variables, secrets, settings, or run history. This keeps the information available for inspection and recovery.
A run that is already active can finish when the severity is Quarantined. A Critical quarantine requests cooperative cancellation. The current node is allowed to return safely, then the runtime stops before starting another node.
When an entry is removed or its severity becomes lower, BaudBound removes the current restriction. It does not automatically enable a script that was quarantined. Review the script and enable it yourself when you are satisfied that it is safe.
An entry can match one of these identities:
Domain matching uses the parsed hostname. It never uses a simple text prefix. A domain entry matches only the exact domain unless the advisory explicitly includes subdomains.
GitHub publisher entries recognize normal repositories, raw files, the GitHub repository API, GitHub Pages, Gists, and raw Gist files. The account name is taken from the trusted request address recorded by the runner. It is not taken from package text that a publisher can edit.
The runner checks the original address and every redirect when it downloads a repository or package. A restricted redirect stops the download before the next request is sent.
A package entry applies only to one exact package hash.
The affected package cannot be approved, enabled, or run when the entry requires quarantine. You can still check for a replacement update when the repository, publisher, domain, and script are not restricted.
The replacement does not inherit trust from the old package. BaudBound downloads it, calculates its hash, validates its script ID and repository information, and checks the Official blacklist again. The replacement is accepted only when the new package passes every normal package and security check.
This behavior lets a publisher replace one affected package without removing protection from the affected file.
Open Security, then find Official blacklist.
This section shows:
Choose Check now to request a fresh copy.
If the API is unavailable, the runner keeps the last complete and valid cache. A failed request never clears known entries. On a first offline start with no cache, the runner continues and reports that blacklist information is unavailable.
The cache is checked during startup before triggers are registered. New entries are also applied when a background refresh completes.
Open Browse Scripts, then choose Repository management.
An affected repository remains visible there even when its scripts are hidden from the browser. The row shows its state and the complete public advisory.
For a restricted repository:
Removing a repository cannot bypass an Official blacklist entry. Scripts already quarantined remain disabled.
Use the block control in Repository management when you no longer want one runner installation to use a repository.
A personal block:
The repository remains visible in management while it is configured. If the repository has been removed, its address remains in a separate blocked repository row so you can remove the personal block later.
Removing a personal block does not automatically enable the repository. It also does not override an active official restriction.
An Official blacklist request contains an ordinary request for the active public records. The API server can observe the runner public IP address, request time, runner user agent, and normal connection metadata.
The request does not include:
The runner requests an explicit public field list. Hidden maintainer notes are not requested, cached, logged, or displayed.
Continue with Script Management for repository and update tasks, or Security Model for the complete trust model.