Skip to content
Open-Source Registry

cargo / baracuda-cutlass / 0.0.1-alpha.110

baracuda-cutlass 0.0.1-alpha.110

bitbison: flagged, behavior flagged, dependencies clean, posture not checked, pipeline clean, 1 of 1 jobs captured 2 detections
processes
187
operations
20K
packages
64
compiler runs
24
connections
2
job time
39s
capture
278 KB
records
37K
bytes / record
7.5

Build behaviourundeclared fetchfetched outside crates.io

run 71c30259-2b85-44f5-bb3d-4fdaef55f308 · built 2026-10-15 · complete

Graph

egress · medium
2

Checks

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

Detections

2
  • Build script ran git
    baracuda-cutlass-sys 0.0.1-alpha.110 › github.com:443
    medium
  • Build script reached github.com
    baracuda-cutlass-sys 0.0.1-alpha.110 › github.com:443
    medium

Detection

mediumwitnessed

Build script ran git

Unexpected build script activity

Subject
baracuda-cutlass-sys 0.0.1-alpha.110
Destination
github.com:443
Jobs
build-test
Rule
buildscript · baracuda

Evidence

  1. Build script ran a download or version-control toolcause

    Tool invocations: 27. Build script: /home/runner/work/baracuda/baracuda/target/release/build/baracuda-cutlass-sys-0b035464eded4109/build_script_build-0b035464eded4109

    by /home/runner/work/baracuda/baracuda/target/release/build/baracuda-cutlass-sys-0b035464eded4109/build-script-build

  2. What the tool didcause

    Recorded activity: used a network connection to github.com:443

    target github.com:443

  3. What the tool didcause

    Recorded activity: wrote: /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0

    target /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0

  4. What the tool didcause

    Recorded activity: wrote: /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0/.git

    target /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0/.git

  5. What the tool didcause

    Recorded activity: wrote: /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0/.git/HEAD

    target /home/runner/.baracuda-cutlass-sys/checkouts/cutlass-4_2_0/.git/HEAD

  6. Tool commandsupport

    Command: /usr/lib/git-core/git -c fetch.negotiationAlgorithm=noop fetch origin --no-tags --no-write-fetch-head --recurse-submodules=no --filter=blob:none --stdin

    by /usr/lib/git-core/git -c fetch.negotiationAlgorithm=noop fetch origin --no-tags --no-write-fetch-head --recurse-submodules=no --filter=blob:none --stdin

  7. Tool commandsupport

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

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

  8. Tool commandsupport

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

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

  9. Additional itemscontext

    … +1006 more

Remediation

Review the command, its network destinations, and the files it wrote. Remove unexpected activity from the build script.

Detection

mediumwitnessed

Build script reached github.com

Unexpected network connection

Subject
baracuda-cutlass-sys 0.0.1-alpha.110
Destination
github.com:443
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. What a build script's fetch becamesupport

    29 files came down; nothing the build compiled, linked or ran

  3. 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-0b035464eded4109/build_script_build-0b035464eded4109

  4. Tool commandsupport

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

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

What came before it

Loading the graph

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-diagnostics2459
  2. cargo/home/runner/.rustup/toolchains/1.99.0-x86_64-unknown-linux-gnu/bin/cargo build --release --locked --message-format=json-render-diagnostics2459
  3. build-script-build/home/runner/work/baracuda/baracuda/target/release/build/baracuda-cutlass-sys-0b035464eded4109/build-script-build3152
  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…3177
  5. git/usr/lib/git-core/git remote-https origin https://github.com/NVIDIA/cutlass.git3154
  6. git-remote-https/usr/lib/git-core/git-remote-https origin https://github.com/NVIDIA/cutlass.git3159

Remediation

The build script connected to the network while compiling. Nothing it downloaded was compiled, linked or run. Build the crate from what the registry ships, or accept the download after reviewing it.

Network

2 peers
  • github.com:443 build code of baracuda-cutlass-sys · git-remote-http · GitHub, Inc. · 29 files undeclared
  • static.crates.io:8080 the package manager · cargo (baracuda) via crates.io · 6,858 files · went into an output ecosystem
Dependencies65Build behaviour
baracuda-build0.0.1-alpha.110
baracuda-core0.0.1-alpha.110
baracuda-cublas0.0.1-alpha.110
baracuda-cublas-sys0.0.1-alpha.110build script
baracuda-cuda-sys0.0.1-alpha.110build script
baracuda-cutlass-kernels-sys0.0.1-alpha.110build script
baracuda-cutlass-sys0.0.1-alpha.110build scriptnetworkruns toolsgithub.com, git
baracuda-driver0.0.1-alpha.110
baracuda-forge0.0.1-alpha.110
baracuda-kernels-types0.0.1-alpha.110
baracuda-types0.0.1-alpha.110
block-buffer0.12.1
cfg-if1.0.4
const-oid0.10.2
cpufeatures0.3.1
crossbeam-deque0.8.7build script
crossbeam-epoch0.9.20build script
crossbeam-utils0.8.22build script
crunchy0.2.4build script, not run
crypto-common0.2.2
digest0.11.3
either1.18.0
float80.7.0
fs20.4.3
glob0.3.4
half2.7.1
hermit-abi0.5.2
hybrid-array0.4.15
itoa1.0.18
ld-linux-x86-64.so.2system library
libc0.2.189build script
libc.so.6system library
libgcc_s.so.1system library
libloading0.8.9
libm.so.6system library
libmvec.so.1system library
memchr2.8.3
num_cpus1.17.0
proc-macro21.0.107build script
quote1.0.47build script
rayon1.12.0
rayon-core1.13.0build script
same-file1.0.6
serde1.0.229build script
serde_core1.0.229build script
serde_derive1.0.229proc macro
serde_json1.0.151build script
sha20.11.0
syn2.0.119
syn3.0.6
thiserror2.0.20build script
thiserror-impl2.0.20proc macro
typenum1.20.1
unicode-ident1.0.24
unpopped-vocab0.17.1
walkdir2.5.0
winapi0.3.9build script, not run
winapi-i686-pc-windows-gnu0.4.0build script, not runprebuilt objects
winapi-util0.1.11
winapi-x86_64-pc-windows-gnu0.4.0build script, not runprebuilt objects
windows-link0.2.1
windows-sys0.61.2
zerocopy0.8.56build script
zerocopy-derive0.8.56proc macro
zmij1.0.23build script

Raw data

capture
278 KB
records
36,951
bytes per record
7.5

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-15 · run 71c30259-2b85-44f5-bb3d-4fdaef55f308

analysis 0.1.0 · 2026-10-15 · 20a5b2e · graph v2