Skip to content

Blueshoe 459 security check#2

Open
ElCaptaine wants to merge 10 commits into
mainfrom
BLUESHOE-459-Security-check
Open

Blueshoe 459 security check#2
ElCaptaine wants to merge 10 commits into
mainfrom
BLUESHOE-459-Security-check

Conversation

@ElCaptaine

@ElCaptaine ElCaptaine commented Mar 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • New security-scan composite action using osv-scanner for dependency vulnerability scanning
  • Reads lock files directly (requirements.txt, poetry.lock, uv.lock, package-lock.json) — no package manager installation needed
  • CVSS severity scores included automatically
  • Optional webhook reporting to /api/reports/osv (compatible with Watchdog)
  • GitHub Step Summary with severity breakdown per ecosystem

What's included

  • actions/security-scan/ — action.yml + 5 shell scripts
  • Test fixtures for pip, poetry, uv, and npm
  • CI test jobs: pip, npm, poetry, uv, skip-all, webhook (against watchdog.blueshoe.de)
  • Full documentation in docs/security-scan.md

What's missing (Phase 2)

  • Container image scanning
  • Gitleaks secret detection

  Composite GitHub Action with pip-audit and npm audit, automatic
  package manager detection (pip/poetry/uv), severity filtering,
  aggregated JSON results with severity_counts, and GitHub Step Summary
  Add test fixtures and CI jobs for Python package manager auto-detection
…ration test

  Optional webhook support for posting raw pip-audit/npm audit JSON to
  any compatible API. Adds CI test against watchdog.blueshoe.de using
  repository secret and variable
…nner

  Single binary scans all lock files directly (requirements.txt, poetry.lock,
  uv.lock, package-lock.json) — no package manager installation needed.
  CVSS severity scores included automatically. Webhook reports to
  /api/reports/osv as single unified payload
@ElCaptaine ElCaptaine requested a review from SteinRobert March 20, 2026 15:47
@ElCaptaine ElCaptaine self-assigned this Mar 20, 2026
Standalone action (security-scan-container) that scans container images
via osv-scanner. Supports Quay.io, AWS ECR, and generic Docker registries.
Includes CI test against alpine:3.17.0 as a public image with known CVEs.
@ElCaptaine ElCaptaine marked this pull request as ready for review March 26, 2026 13:19
Standalone action (security-gitleaks) that detects leaked secrets using
gitleaks. Supports git history and directory-only scan modes, custom
configs, baselines, and webhook reporting. Includes CI tests with a
fake-secret fixture and a clean-scan verification.
The previous EXAMPLE keys are in gitleaks' built-in allowlist and were
silently skipped. Also removed the custom config input from the test
since default rules detect the new fixture secrets.
Root .gitleaks.toml allowlists the fixture path, causing gitleaks to
skip findings. Pass an explicit config without allowlist from the fixture
directory. Also add verbose logging to scan script for debugging
…llowlists

Previous fake secrets were filtered by gitleaks' built-in stopwords
(alphabetical sequences) and regex allowlists. Verified locally that
the new values trigger github-pat and generic-api-key rules.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant