Secure

This repository is the central, auditable inventory of security evidence for the uug-ai organization. It gives security officers and engineering teams one place to review software composition, known vulnerabilities, security-control coverage, and trends across projects.

This repository is public by design so customers, users, security officers, and engineering teams can inspect the available evidence. A missing or stale record is a coverage gap, not proof that a project has no vulnerabilities. Everything committed here is public information and must be approved for external disclosure.

Security guidance

The container image hardening guide documents image build, release, and customer runtime expectations, imported from UUG Learn for further development here. This guidance describes required practices; it is not evidence that a particular image implements them or a claim of CIS compliance.

Evidence inventory

Area	Location	State
SPDX SBOMs	sboms/	Automated daily
SBOM coverage	sboms/index.json	Automated daily
Container vulnerability scans	containers/	Automated daily
Container scan coverage	containers/index.json	Awaiting first scan
Critical/high vulnerability aggregate	cves/	Automated with container scans
Critical/high occurrence data	cves/index.json	Awaiting first scan
Security metrics	metrics/	Planned
Protection controls	controls/control-register.md	Initial assessment register

Container image security overview

Generated at 2026-11-10T03:48:21Z from the newest tagged GHCR image available for each approved project. Scores use the highest detected severity: 100 clean, 80 low, 60 medium, 30 high, and 0 critical. An unavailable image is a coverage gap, not a clean result.

Repository	Scan	Risk	Score	Tag	Critical	High	Medium	Low	Fixable C/H	Report
factory	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-anpr	scanned	High	30/100	latest	0	3	1	0	0/3	Trivy
hub-api	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-audit	scanned	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-cleanup	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-frontend	stale	Clean	100/100	latest	0	0	0	0	0/0	Trivy
hub-loitering	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-monitor-device	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-objecttracking	scanned	High	30/100	latest-gpu	0	20	896	125	0/20	Trivy
hub-pipeline-analysis	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-pipeline-classifier	scanned	Critical	0/100	latest	32	646	3050	1534	22/175	Trivy
hub-pipeline-counting	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-pipeline-dominantcolors	scanned	High	30/100	latest	0	5	2	0	0/5	Trivy
hub-pipeline-event	scanned	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-pipeline-export	scanned	High	30/100	latest	0	1	2	0	0/1	Trivy
hub-pipeline-monitor	stale	High	30/100	latest	0	22	15	3	0/22	Trivy
hub-pipeline-notification	scanned	High	30/100	latest	0	1	2	0	0/1	Trivy
hub-pipeline-notification-test	scanned	High	30/100	latest	0	1	2	0	0/1	Trivy
hub-pipeline-redaction	scanned	High	30/100	latest	0	3	1	0	0/3	Trivy
hub-pipeline-sequence	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-pipeline-sprite	scanned	High	30/100	latest	0	5	2	0	0/5	Trivy
hub-pipeline-throttler	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-pipeline-thumbnail	scanned	High	30/100	latest	0	5	2	0	0/5	Trivy
hub-proxy	unavailable	Unavailable	-	-	0	0	0	0	0/0	-
hub-reactivatesubscriptions	unavailable	Unavailable	-	-	0	0	0	0	0/0	-
hub-vault-forwarder	unavailable	Unavailable	-	-	0	0	0	0	0/0	-
hub-vlm	scanned	High	30/100	latest	0	5	2	0	0/5	Trivy
hub-workflows	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
hub-workflows-forwarder	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy
vault	stale	Unknown	40/100	latest	0	0	0	0	0/0	Trivy

SBOM quality overview

Generated at 2026-11-10T02:24:36Z. Quality combines document metadata (20%), package identity (30%), licensing (20%), provenance (15%), and relationships (15%).

Legend: 🟢 85-100, 🟡 70-84, 🟠 50-69, 🔴 0-49 or unavailable. This measures SBOM completeness, not vulnerability severity.

Repository	Collection	Quality	Score	Packages	Versioned	Licensed	PURL	Details
factory	collected	🟠 Needs work	69/100	1536	100%	99%	100%	Breakdown · SPDX
hub-anpr	collected	🟠 Needs work	68/100	73	100%	82%	100%	Breakdown · SPDX
hub-api	collected	🟠 Needs work	69/100	192	100%	92%	100%	Breakdown · SPDX
hub-audit	unavailable	🔴 Unavailable	0/100	0	0%	0%	0%	Breakdown
hub-cleanup	collected	🟠 Needs work	68/100	46	100%	85%	100%	Breakdown · SPDX
hub-frontend	collected	🟠 Needs work	69/100	1330	100%	99%	100%	Breakdown · SPDX
hub-loitering	collected	🟠 Needs work	68/100	67	100%	85%	100%	Breakdown · SPDX
hub-monitor-device	collected	🟠 Needs work	68/100	75	100%	89%	100%	Breakdown · SPDX
hub-objecttracking	collected	🟠 Needs work	68/100	68	100%	85%	100%	Breakdown · SPDX
hub-pipeline-analysis	collected	🟠 Needs work	68/100	80	100%	85%	100%	Breakdown · SPDX
hub-pipeline-classifier	collected	🟠 Needs work	68/100	62	100%	89%	100%	Breakdown · SPDX
hub-pipeline-counting	collected	🟠 Needs work	68/100	66	100%	83%	100%	Breakdown · SPDX
hub-pipeline-dominantcolors	collected	🟠 Needs work	68/100	76	100%	91%	100%	Breakdown · SPDX
hub-pipeline-event	collected	🟠 Needs work	68/100	47	100%	85%	100%	Breakdown · SPDX
hub-pipeline-export	collected	🟠 Needs work	68/100	75	100%	88%	100%	Breakdown · SPDX
hub-pipeline-monitor	collected	🟠 Needs work	69/100	79	100%	90%	100%	Breakdown · SPDX
hub-pipeline-notification	collected	🟠 Needs work	68/100	108	100%	89%	100%	Breakdown · SPDX
hub-pipeline-notification-test	collected	🟠 Needs work	68/100	71	100%	85%	100%	Breakdown · SPDX
hub-pipeline-redaction	collected	🟠 Needs work	68/100	72	100%	82%	100%	Breakdown · SPDX
hub-pipeline-sequence	collected	🟠 Needs work	68/100	84	100%	83%	100%	Breakdown · SPDX
hub-pipeline-sprite	collected	🟠 Needs work	68/100	79	100%	82%	100%	Breakdown · SPDX
hub-pipeline-throttler	collected	🟠 Needs work	68/100	59	100%	85%	100%	Breakdown · SPDX
hub-pipeline-thumbnail	collected	🟠 Needs work	68/100	83	100%	84%	100%	Breakdown · SPDX
hub-proxy	collected	🟠 Needs work	67/100	27	100%	74%	100%	Breakdown · SPDX
hub-reactivatesubscriptions	collected	🟠 Needs work	68/100	60	100%	82%	100%	Breakdown · SPDX
hub-vault-forwarder	collected	🟠 Needs work	69/100	8	100%	88%	100%	Breakdown · SPDX
hub-vlm	unavailable	🔴 Unavailable	0/100	0	0%	0%	0%	Breakdown
hub-workflows	collected	🟠 Needs work	69/100	142	100%	91%	100%	Breakdown · SPDX
hub-workflows-forwarder	unavailable	🔴 Unavailable	0/100	0	0%	0%	0%	Breakdown
vault	collected	🟠 Needs work	69/100	1233	100%	99%	100%	Breakdown · SPDX

SBOM collection

The Collect product SBOMs workflow runs daily at 02:17 UTC and can also be started manually. It:

1. Lists repositories visible to the read-only organization token and selects names beginning with hub plus the exact factory and vault repositories, except repositories explicitly excluded after retirement.
2. Downloads each selected repository's SPDX SBOM from GitHub's Dependency Graph API.
3. Writes collection metadata to sboms/<repository>/status.json and, when available, the document to sboms/<repository>/sbom.spdx.json.
4. Scores document metadata, package identity, licensing, provenance, and SPDX relationships, then updates the quality table above.
5. Updates sboms/index.json with collection status, quality metrics, and coverage totals.
6. Preserves the last successful document and marks it stale when a refresh fails.
7. Commits changed evidence with the repository-scoped GitHub Actions token. Rejected non-fast-forward pushes are rebased onto the latest main and retried up to three times.

The collector ignores every repository outside hub*, factory, and vault. It also excludes the retired hub-background-notifcation-digest, hub-license, hub-mobile, hub-pipeline, hub-pipeline-classifier-yolov3, and hub-pipeline-licenseplate repositories. When the scope changes, generated directories and index entries that are no longer selected are removed during the next successful collection. Archived or private target repositories are included when visible to the token, so grant private access only when the repository name and SBOM are approved for public disclosure.

Container image scanning

The Scan product container images workflow runs separately each day at 03:47 UTC and can be started manually. It uses the approved repositories in sboms/index.json, discovers the newest tagged ghcr.io/uug-ai/<repository> package version, scans its immutable digest with Trivy, and writes raw reports plus summary metadata under containers/. It also groups critical and high findings by advisory identifier under cves/, counting each affected package record as one occurrence and listing the unique affected repositories and package versions. Medium and lower findings remain available in the raw reports but are not included in the CVE aggregate.

Projects without a matching tagged image remain visible as unavailable. Transient package or scanner failures preserve the last successful report as stale. The root overview scores the highest detected severity as 100 clean, 80 low, 60 medium, 30 high, or 0 critical and shows vulnerability and fixable critical/high counts. This is a triage score, not a guarantee that an image is secure.

Required setup

Grant the existing TOKEN organization secret to this repository. The workflow uses it only to read organization repositories and their SBOMs. The token should ideally be owned by a dedicated automation account and limited to:

• Repository access to the hub*, factory, and vault repositories whose SBOMs are approved for public disclosure.
• Contents: read repository permission; metadata read access is implicit.
• read:packages scope and access to each GHCR package approved for public vulnerability reporting.
• No write permissions.

An existing token with broader permissions will work, but reducing it to these permissions limits the impact of accidental exposure or workflow compromise.

The repository's Actions settings must allow GITHUB_TOKEN to write contents so the workflow can push refreshed evidence. If main is protected against direct pushes, grant the security bot an appropriate bypass or change the final step to open a pull request.

GitHub Dependency Graph must be enabled for each target repository. Target repositories where it is disabled or inaccessible remain visible in the index as unavailable rather than silently disappearing.

Trust model

• The evidence repository is public to provide transparent, reviewable security information.
• Cross-repository credentials are read-only and scoped to collection.
• Generated records retain their source repository and API endpoint.
• Workflow actions are pinned to immutable commit SHAs.
• Collection errors are evidence and remain visible in the coverage index.
• Changes to controls and manually maintained assessments require review.

Do not store credentials, private repository evidence that has not been approved for disclosure, exploit details, customer data, or confidential incident material in this repository. Use the approved private incident process for sensitive operational information.

Development

The collector uses only the Go standard library.

GOWORK=off go test ./...
GH_TOKEN=<read-only-token> GOWORK=off go run ./cmd/collect-sboms
GOWORK=off go run ./cmd/collect-sboms -refresh-existing
export GH_TOKEN=<read-only-token>
export TRIVY_USERNAME=<token-owner>
export TRIVY_PASSWORD="$GH_TOKEN"
GOWORK=off go run ./cmd/scan-containers