Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
Startup-SBOM — A tool to reverse engineer and inspect the RPM and APT databases to list all the packages along with executables, service, versions and CVE. | Kitploit
도구/GitHubGitHub/morpheuslord/startup-sbom
Vulnerability ScannersContainer SecurityVulnerability AnalysisReverse EngineeringConfiguration AuditingCloud SecuritySupply Chain Security
GitHubmorpheuslord/startup-sbom

Startup-SBOM

A tool to reverse engineer and inspect the RPM and APT databases to list all the packages along with executables, service, versions and CVE.

저장소 보기
172913일 전Kitploit 검토 완료
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

Startup-SBOM logo

Startup-SBOM

What runs at boot, what it is made of, and how it can be attacked.

PyPI version Python versions CI Documentation License: MIT Listed in the CycloneDX Tool Center

Read the documentation →

Startup-SBOM statically analyses a Linux root filesystem, container or image and answers three questions most SBOM tools can't:

  1. Vulnerability → threat. Not "openssl has 14 CVEs", but "an unauthenticated remote attacker who can reach TCP/22 could exploit CVE-2024-6387 in openssh-server (sshd, ssh.service, enabled at boot, runs as root) to execute code as root — EPSS 0.94, known exploited. Fix: upgrade to 1:9.2p1-2+deb12u3." Every finding is placed in context: is it reachable at boot, through which service, linked by which binary, what triggers it (boot, socket, timer, cron, D-Bus, udev device event, setuid binary, kernel) and who can fire that trigger, as which user, network-exposed, mitigated by which systemd hardening, mapped to MITRE ATT&CK, with a CISA SSVC decision (Track / Track* / Attend / Act).
  2. Chained attacks. A privilege-state attack graph (remote → local:<user> → root → container escape → persistence) built from vulnerabilities and misconfigurations (setuid/capability binaries, privileged containers, mounted Docker socket, kernel CVEs, writable units), pruned by hardening and ranked by likelihood × impact.
  3. Supply-chain blast radius. A vendor → source package → binary package → file → service graph built from real code-loading edges (ELF DT_NEEDED, .note.dlopen, ld.so.preload, interpreters). It catches the xz → liblzma → libsystemd → sshd class of problem, which package dependencies alone miss. It also flags provenance risks: third-party repositories, unsigned or locally built packages, unmanaged binaries, modified files and EOL distributions.

It is read-only by design: nothing in the target is mounted, extracted or modified, symlinks can never escape the analysed root, and in the default static mode nothing in the target is executed. The opt-in chroot mode (--mode chroot) runs a few of the target's own tools to confirm the static results, only inside an unprivileged, read-only, network-less bubblewrap sandbox.

Install

uv tool install startup-sbom        # or: pipx install startup-sbom
uvx startup-sbom --help             # run without installing
docker run --rm ghcr.io/morpheuslord/startup-sbom --help

The core scanner has no heavy dependencies; optional features are extras:

ExtraAdds
startup-sbom[tui]Interactive terminal UI (startup-sbom tui)
startup-sbom[pdf]PDF reports (-f pdf, Typst; PDF/A-3u + PDF/UA-1 by default)
startup-sbom[ai]AI analysis across multiple LLM providers, DuckDuckGo search, MCP server
startup-sbom[agents-server]A2A and ACP agent servers
startup-sbom[all]Everything above
uv tool install "startup-sbom[all]"

From source:

git clone https://github.com/morpheuslord/Startup-SBOM && cd Startup-SBOM
uv sync
uv run startup-sbom --help

Python ≥ 3.11 on Linux, macOS or Windows. Everything except host: mode and live container acquisition is pure Python and host-OS independent.

Usage

# A mounted disk or extracted rootfs
startup-sbom scan dir:/mnt/target_root -f html -f cyclonedx -o out/

# A running or stopped container (docker / podman / nerdctl)
startup-sbom scan docker:web -f json -f sarif

# Images without a container engine
startup-sbom scan docker-archive:./image.tar      # docker/podman save
startup-sbom scan oci-dir:./layout                 # OCI image layout
startup-sbom scan tar:./rootfs.tar.zst             # docker export / rootfs tarball

# The machine you are on (Linux)
sudo startup-sbom scan host: -f markdown

# CI gate: fail when anything warrants immediate action
startup-sbom scan oci-archive:img.tar -f sarif --fail-on act

# Confirm with the target's own tools in a sandbox (needs bubblewrap), keep a journal
startup-sbom scan dir:/mnt/target_root --mode chroot --journal scan.jsonl -f html
OptionMeaning
-f, --formatjson, cyclonedx, spdx, sarif, openvex, cdx-vex, markdown, html, dot, mermaid, pdf (repeatable)
-o, --outputOutput directory (default ./startup-sbom-out), or - to stream one format to stdout
--offlineNo network; use cached intelligence only
--sourcesVulnerability sources: osv, arch, nvd (opt-in, set NVD_API_KEY), or none
--no-epss, --no-kev, --no-eolSkip exploit-prediction, known-exploited and end-of-life enrichment
--no-language-packagesSkip Python/npm/Go/Java/Rust inventory
--no-link-analysisSkip ELF library reachability
--integrityVerify installed files against package-database digests
--boot-timing FILEsystemd-analyze plot SVG or blame output captured on the target
--modestatic (default, reads files only), chroot (also run the target's loader, systemctl and package manager in a bubblewrap sandbox) or auto (chroot when possible)
--no-derivative-fallbackDon't match rolling Debian derivatives (Kali, …) against Debian testing advisories
--no-cvss-impact-gateLet confidentiality-only (I:N/A:N) flaws count as code execution
--platformSelect a platform from a multi-arch image, e.g. linux/arm64
--cdx-specCycloneDX 1.5, 1.6 (default) or 1.7
--fail-onlow … critical (vulnerability severity) or attend / act (SSVC)
--prefetch-intelFetch advisories, exploit references and articles for the top findings (opt-in, online)
--live / --no-liveLive dashboard of stages, digests and raw operations on stderr (default: on a terminal)
--journal FILEWrite every stage, raw operation, digest and analyst note as JSON lines
--ai-liveAn LLM comments on each stage while the scan runs (ai extra; display-only)
--ai-provider, --ai-model, --ai-budgetLive analyst provider, provider:model-id, and spending cap in USD (default 0.10)
-q, -v, --debugQuiet / verbose / debug

Other commands: startup-sbom tui (interactive UI), startup-sbom ai … (AI analysis and agent servers), startup-sbom intel … (CVE intelligence lookup), startup-sbom db update|status|clear (cache KEV/EPSS for offline use), startup-sbom schema (JSON Schema of the native report), startup-sbom version.

Exit codes: 0 success, 1 --fail-on threshold reached, 2 usage or target error, 3 internal error.

Outputs

도구 다운로드

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    732
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    405
  • 4

    redforge

    cybersecurity91/redforge

    브라우저 측 레드 팀 툴킷으로, 정찰, 페이로드 생성, 자격 증명 공격, 암호화, 인코딩 및 참여 보고를 위한 102개의 오프라인 도구를 제공합니다.

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI 네이티브 사이버보안을 위한 행동 체계—의도가 통제된 실행이 되고, 증거가 운영 메모리가 되며, 모든 운영이 다음 운영을 개선하는 곳.

    261
  • 6

    antifox

    antifox-ai/antifox

    정찰, 공격 표면 탐색, 익스플로잇 검증, 증거 기반 보고서 전달을 수행하는 AI 멀티 에이전트 자율 침투 테스트 플랫폼입니다.

    259

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →