Skip to content
Open-Source Registry

cargo / baracuda-cutlass-sys / 0.0.1-alpha.94

baracuda-cutlass-sys 0.0.1-alpha.94

bitbison: flagged, behavior flagged, dependencies clean, posture not checked, pipeline clean, 1 of 1 jobs captured 1 detection
processes
220
operations
7.9K
packages
10
compiler runs
1
connections
2
job time
8s
capture
138 KB
records
15K
bytes / record
9.0

Build behaviourits build script reached github.comits build script ran gitundeclared fetchfetched outside crates.io

run d568a676-003a-44ef-8c03-5e3067dfa469 · built 2026-10-12 · complete

Artifact

file · retained · product · graph v2
1

Checks

13 of 14 clear Network activity
Build behavior▲✓✓✓✓✓✓✓
Supply chain✓✓✓✓✓
Pipeline✓

Detections

1
  • Build code opened a network connection
    baracuda-cutlass-sys 0.0.1-alpha.94 › github.com:443
    high

Detection

highwitnessed

Build code opened a network connection

Unexpected network connection

Subject
baracuda-cutlass-sys 0.0.1-alpha.94
Destination
github.com:443
Reaches
Jobs
build-test
Rule
egress

Evidence

  1. Connection outside the process’s allowed destinationscause

    connection to github.com:443, opened by git-remote-http

    subject github.com:443

    by /usr/lib/git-core/git-remote-https origin https://github.com/NVIDIA/cutlass.git

  2. Connection opened by a build script or child processsupport

    the opener descends from the build script at /home/runner/work/baracuda/baracuda/target/release/build/baracuda-cutlass-sys-51484978ecd5bcfc/build_script_build-51484978ecd5bcfc

Processes

build-test

cargo›cargo›build-script-build›git›git›git-remote-https

Ran
/usr/lib/git-core/git-remote-https origin https://github.com/NVIDIA/cutlass.git
Invoked by
cargo build --release --locked --message-format=json-render-diagnostics
Lineage · 6 processes
  1. cargocargo build --release --locked --message-format=json-render-diagnostics2453
  2. cargo/home/runner/.rustup/toolchains/1.99.0-x86_64-unknown-linux-gnu/bin/cargo build --release --locked --message-format=json-render-diagnostics2453
  3. build-script-build/home/runner/work/baracuda/baracuda/target/release/build/baracuda-cutlass-sys-51484978ecd5bcfc/build-script-build2522
  4. gitgit clone --depth 1 --filter=blob:none --sparse --no-recurse-submodules --branch v4.2.0 https://github.com/NVIDIA/cutlass.git /home/runner/.baracuda-cutlass-sys…2527
  5. git/usr/lib/git-core/git remote-https origin https://github.com/NVIDIA/cutlass.git2524
  6. git-remote-https/usr/lib/git-core/git-remote-https origin https://github.com/NVIDIA/cutlass.git2526

Remediation

Review the process and its owning build step. Remove unnecessary requests; move required downloads to a declared dependency-fetch step.

Network

2 peers
  • github.com:443 baracuda-cutlass-sys's own build code · git-remote-http · GitHub, Inc. · 28 files undeclared
  • static.crates.io:8080 the package manager · cargo (baracuda) via crates.io · 3,668 files · went into an output ecosystem
Dependencies10Build behaviour
winapi-i686-pc-windows-gnu0.4.0build script, not runprebuilt objects
winapi-x86_64-pc-windows-gnu0.4.0build script, not runprebuilt objects
ld-linux-x86-64.so.2system library
libc0.2.189build script
libc.so.6system library
libgcc_s.so.1system library
libm.so.6system library
libmvec.so.1system library
winapi0.3.9build script, not run
fs20.4.3

Raw data

capture
138 KB
records
15,332
bytes per record
9.0

Loading a sample of the capture

Want to see more? E-mail us at hello@bitbison.io about your use case.

1 of 1 jobs captured: build-test success · Generated 2026-10-12 · run d568a676-003a-44ef-8c03-5e3067dfa469

analysis 0.1.0 · 2026-10-11 · d6246d3 · graph v2