dependency-track-upload
/dependency-track-upload
Publikuje pliki SBOM CycloneDX w Dependency-Track lub na serwerze TEA i uruchamia cdxgen jako usługę generującą BOM.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 8
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Publikuje pliki SBOM CycloneDX w Dependency-Track lub na serwerze TEA i uruchamia cdxgen jako usługę generującą BOM.
Oryginalny opis (EN)
Publishes CycloneDX BOMs to Dependency-Track or a TEA (Transparency Exchange API) server from cdxgen, and runs cdxgen in HTTP server mode to generate BOMs on demand for local paths, Git URLs, or package URLs. Use when asked to upload or submit an SBOM to Dependency-Track, register a project or parent-child project hierarchy, publish to a TEA collection, or run cdxgen as an SBOM service or API.
Jak działa
- Plugin settings
- Confirm before uploading
- Credentials
- Dependency-Track submission
- TEA publishing
- Server mode
- Reference
Podgląd SKILL.md
---
name: dependency-track-upload
description: Publishes CycloneDX BOMs to Dependency-Track or a TEA (Transparency Exchange API) server from cdxgen, and runs cdxgen in HTTP server mode to generate BOMs on demand for local paths, Git URLs, or package URLs. Use when asked to upload or submit an SBOM to Dependency-Track, register a project or parent-child project hierarchy, publish to a TEA collection, or run cdxgen as an SBOM service or API.
disable-model-invocation: true
---
# Publish BOMs and run cdxgen as a service
Two related capabilities: pushing a BOM to a platform, and exposing cdxgen over
HTTP.
Read [reference/safety.md](../../reference/safety.md) first. Both halves of this
skill touch the network and credentials, so the constraints below are not
optional.
## Plugin settings
Claude Code replaces the `${user_config.*}` values in this table with the
options the user set for the plugin. Other clients show the text as written. A
value counts as set only when it is not empty and does not start with `${`;
otherwise ignore it and follow the "When not set" column. The settings hold no
keys or tokens, and the rule against asking for, printing or writing one still
applies.
| Setting | Value | When not set |
| --------------------------- | ------------------------------------- | ----------------------------- |
| Dependency-Track server URL | `${user_config.dependency_track_url}` | Ask the user for the URL |
| TEA endpoint | `${user_config.tea_endpoint}` | Ask the user for the endpoint |
A configured URL is a suggestion for `--server-url` or `--tea-publish`. Show it
to the user and get a yes before any upload, as described below.
## Confirm before uploading
Uploading a BOM **publishes it to an external system**. Before any submission:
1. Confirm the destination URL with the user.
2. Confirm the project name, version, and parent, since a wrong value creates or overwrites the wrong project.
3. Confirm the BOM contents are safe to send — a BOM may carry AI/MCP configuration, host inventory, or trust material. Review emitted properties first.
Never invent a server URL, project ID, or API key. If a value is missing, ask.
## Credentials
**Never ask the user to paste an API key into the conversation, and never write
one into a command line or a file.** Pass credentials through the environment
that cdxgen already reads, and let the user set it in their own shell:
```bash
cdxgen -o /absolute/path/to/bom.json \
--server-url https://deptrack.example.com \
--project-name my-app --project-version 1.2.3 \
/absolute/path/to/project
```
with `CDXGEN_*`/`TEA_TOKEN`-style variables set by the user beforehand. The TEA
bearer token in particular is designed for this: it is sent only as an
`Authorization` header, never logged, and can come from `TEA_TOKEN`.
If a key does appear in your context anyway, do not echo it back.
## Dependency-Track submission
```bash
cdxgen -o /absolute/path/to/bom.json \
--server-url https://deptrack.example.com \
--project-name my-app \
--project-version 1.2.3 \
/absolute/path/to/project
```
| Flag | Purpose |
| -------------------------- | -------------------------------------------------------------------- |
| `--server-url` | Dependency-Track URL |
| `--api-key` | API key (prefer the environment; see above) |
| `--project-name` | Project name; defaults to the directory name |
| `--project-version` | Project version |
| `--project-id` | Project ID — supply this **or** name and version together |
| `--project-tag` | Project tag; repeatable |
| `--project-group` | Project group |
| `--parent-project-id` | Parent project ID |
| `--parent-project-name` | Parent project name |
| `--parent-project-version` | Parent project version |
| `--auto-create` | Let Dependency-Track create the project if absent |
| `--is-latest` | Mark this version as latest |
| `--skip-dt-tls-check` | Skip TLS verification |
Identify the project **either** by `--project-id` **or** by
`--project-name` plus `--project-version` together. Half of the latter pair is
not enough.
`--skip-dt-tls-check` disables certificate verification. Only suggest it for a
known-internal host with a self-signed certificate, and say what it turns off.
### Monorepo hierarchies
Use the parent flags to nest per-module projects under one parent, so
Dependency-Track shows the aggregate:
```bash
cdxgen -o /absolute/path/to/module-bom.json \
--server-url https://deptrack.example.com \
--parent-project-name my-platform --parent-project-version 2026.1 \
--project-name my-platform-api --project-version 1.2.3 \
/absolute/path/to/module
```
### Host allowlisting
Keep `CDXGEN_ALLOWED_HOSTS` narrow. Server-side Dependency-Track submission
interprets a wildcard entry such as `*.example.com` as **real subdomains only**,
never as a suffix match — so `*.example.com` will not match
`evil-example.com`, and it also will not match `example.com` itself. Prefer
exact hosts.
## TEA publishing
Publish the BOM as a TEA Artifact in a Collection (draft publisher API):
```bash
cdxgen -o /absolute/path/to/bom.json \
--tea-publish https://tea.example.com \
--tea-collection-name "my-app sbom" \
--tea-author-name "Prabhu Subramanian" \
--tea-author-email prabhu@appthreat.com \
/absolute/path/to/project
```
| Flag | Purpose |
| ------------------------ | ---------------------------------------------------------- |
| `--tea-publish` | TEA server URL |
| `--tea-collection-name` | Artifact name; defaults to `<project> sbom` |
| `--tea-leaf-identifier` | Leaf identifier |
| `--tea-artifact-url` | Artifact URL |
| `--tea-author-name`, `--tea-author-email` | Attribution |
| `--tea-reason` | Reason recorded with the publication |
| `--tea-token` | Bearer token; prefer `TEA_TOKEN` in the environment |
| `--tea-fetch` | Fetch from a TEA server |
This is a **draft** publisher API. Tell the user it may change.
## Server mode
```bash
cdxgen --server
cdxgen --server --server-host 0.0.0.0 --server-port 8080
```
Default bind is `127.0.0.1:9090`. Via the container image:
```bash
docker run --rm -v /tmp:/tmp -p 9090:9090 -v $(pwd):/app:rw \
-t ghcr.io/cdxgen/cdxgen -r /app --server --server-host 0.0.0.0
```
`--server-host 0.0.0.0` exposes the service on every interface. Only suggest it
for a container or a host where that is intended, and say so — the default
loopback bind exists for a reason.
### Using the API
Poll `/health` first, then POST to `/sbom` with a JSON body or query
parameters. Arguments mirror the CLI: `path`, `url`, `type`, and the rest.
`url` accepts Git URLs (`https://...git`, `ssh://...`, `git@...`) and package
URLs (`pkg:npm/...`, `pkg:pypi/...`, `pkg:gem/...`, `pkg:cargo/...`,
`pkg:pub/...`, `pkg:github/...`, `pkg:bitbucket/...`, `pkg:maven/...` with a
version, `pkg:composer/...`, `pkg:generic/...` with `vcs_url` or
`download_url`).
Pass `GITHUB_TOKEN` via the environment when scanning private repositories.
API specification: `lib/server/openapi.yaml` in the repository, viewable in
Swagger Editor.
### Server mode is a remote code path
The server generates BOMs for paths and URLs it is given, which means it clones
repositories and may run package managers on request. Treat it as a privileged
service:
- keep it bound to loopback unless there is a reason not to
- keep `CDXGEN_ALLOWED_HOSTS` narrow
- do not expose it to untrusted callers
## Reference
- Server usage: <https://cdxgen.github.io/cdxgen/#/SERVER>
- Environment variables: <https://cdxgen.github.io/cdxgen/#/ENV>
- Allowed hosts and commands: <https://cdxgen.github.io/cdxgen/#/ALLOWED_HOSTS_AND_COMMANDS>
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · cdxgen/cdxgen | 100 | Apache-2.0 |
| cdxgen/cdxgen | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki ce5fb1f01d49 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100sbom-generate
Generuje SBOM w formacie CycloneDX z kodu źródłowego przez OWASP cdxgen: wybór typu projektu, monorepo, licencje i eksport do SPDX. - 100sbom-generate
Generuje SBOM w formacie CycloneDX z kodu źródłowego przez cdxgen dla ponad 30 ekosystemów, także w monorepo. Przydaje się, gdy trzeba zrobić inwentarz zależności. - 90chain-sbom
Projektuje pipeline generowania SBOM: format, narzędzia i integracja z CI/CD, na przykład z CycloneDX. - 95create-sbom
Dodaje do istniejącego pipeline'u Harness krok generowania SBOM przez Harness SCS dla obrazów kontenerów i repozytoriów, z Syft lub cdxgen, formatem SPDX albo CycloneDX i atestacją. - 100software-bill-of-materials-sbom-spdx-cyclonedx
Generuje i audytuje listę składników oprogramowania (SBOM) w standardach SPDX i CycloneDX. - 100sbom-generation
Tworzy SBOM w CycloneDX i SPDX dla kodu, kontenerów i plików binarnych, dołącza je do wydań i sprawdza kompletność. Przydaje się przy wymogach klientów i regulatorów.