sharang/compliance-scanner-agent
1
0
Fork 0
Code Issues 64 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

docs: rebrand Certifai -> Prüfwerk (user-facing name)
CI / Check (push) Skipped
CI / Detect Changes (pull_request) Skipped
Details
CI / Deploy Agent (pull_request) Skipped
Details
CI / Deploy Dashboard (pull_request) Skipped
Details
CI / Deploy Docs (pull_request) Skipped
Details
CI / Deploy MCP (pull_request) Skipped
Details
CI / Check (pull_request) Failing after 1m55s
Details

Browse Source 
The product is renamed Certifai -> Prüfwerk. This changes only the user-facing
brand text in the documentation (docs/**, VitePress title/name). It does NOT
touch functional identifiers that happen to contain "certifai" (the Docker
network, Keycloak realm/client, Harbor image project, the compliance-* crate
names, or the repo name) — those are infra-coupled and need a separate,
coordinated migration.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EgxGHn22YEfQz5fLHSHkLv
This commit is contained in:
Sharang Parnerkar
2026-09-02 09:53:45 +02:00
co-authored by Claude Opus 4.8
parent e0c54c4659
commit 5ad9d2d77c
15 changed files with 59 additions and 59 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guide/repositories.md
+4 -4
View File
@@ -1,6 +1,6 @@
# Adding Repositories
Repositories are the core resource in Certifai. Each tracked repository is scanned on a schedule, and its results are available across all features -- findings, SBOM, code graph, AI chat, and issue tracking.
Repositories are the core resource in Prüfwerk. Each tracked repository is scanned on a schedule, and its results are available across all features -- findings, SBOM, code graph, AI chat, and issue tracking.
## Adding a Repository
@@ -20,11 +20,11 @@ The repository appears in the list immediately. It will not be scanned until you
**Public repositories** can be cloned using an HTTPS URL with no additional setup.
**Private repositories** require SSH access. When you add a repository with an SSH URL (e.g. `git@github.com:org/repo.git`), Certifai uses an SSH deploy key to authenticate.
**Private repositories** require SSH access. When you add a repository with an SSH URL (e.g. `git@github.com:org/repo.git`), Prüfwerk uses an SSH deploy key to authenticate.
### Getting the SSH Public Key
To grant Certifai access to a private repository:
To grant Prüfwerk access to a private repository:
1. Go to the **Repositories** page
2. The platform's SSH public key is available for copying
@@ -34,7 +34,7 @@ To grant Certifai access to a private repository:
- **Gitea**: Repository Settings > Deploy Keys > Add Deploy Key
::: tip
Deploy keys are scoped to a single repository and are read-only by default. This is the recommended approach for granting Certifai access to private code.
Deploy keys are scoped to a single repository and are read-only by default. This is the recommended approach for granting Prüfwerk access to private code.
:::
## Configuring an Issue Tracker