Package evidence

@gitlab/[email protected]

Large Javascript Payload: 9558466 bytes

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published: 101Established · −30% score
First published: Sep 2025
Publisher: GitLab CI/CD

Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarball Add to CI gate

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@gitlab/[email protected]"],"fail_on":"review"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@gitlab/[email protected]"],"fail_on":"review"}'

PublisherGitLab CI/CD

Artifact bytes12,265,331

Previous version8.99.0

Published2026-06-04T13:08:47.721Z

SHA-2561d92315372db16579e677a1de0f110afb94fe1a37fa73c25fa362e2f49d1398f

Why flagged

What the scanner saw

Large Javascript Payload: 9558466 bytes

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low

5h agoLast checked

lowRisk

0Score

8.100.0Version

Status history (1 event)

new → available5h ago · risk low · score 0 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Large Javascript Payload	package/dist/index.js	9558466 bytes	0
low	Large Javascript Payload	package/dist/sandbox_worker.js	3871012 bytes	0

Manifest

Package metadata

Scripts19

buildtsc --noEmit
build:binary./scripts/compile_executables.sh
build:bundle./scripts/build.sh
build:debugbun ./scripts/bun_build_debug.ts
build:dev-binary./scripts/compile_executables.sh local-dev
bundle./scripts/build.sh
debug:builtbun run turbo -- run build:debug --filter=@gitlab/duo-cli && node --inspect-brk=127.0.0.1:9229 dist/index.js
debug:terminalbun run turbo -- run build:debug --filter=@gitlab/duo-cli && bun ./scripts/launch_debug_terminal.ts
dev:watchbun --conditions=_ts-source --watch ./src/index.tsx
dev:watch-toolsbun ./scripts/dev_with_tools.ts
docsbun ./scripts/gen_docs.ts
docs:checkbun ./scripts/gen_docs.ts --check
sign:binary./scripts/sign_executables.sh
startbun run turbo -- run bundle --filter=@gitlab/duo-cli && node --use-system-ca dist/index.js
testNODE_OPTIONS='--experimental-vm-modules' jest
test:debugNODE_OPTIONS='--experimental-vm-modules --inspect-brk' jest --runInBand --no-cache
test:e2ebun run turbo -- run bundle --filter=@gitlab/duo-cli && bun run build:dev-binary && NODE_OPTIONS='--experimental-vm-modules' jest --config jest.e2e.config.js '--testMatch=<rootDir>/test/e2e/*.e2e.test.ts'
test:network-e2ebun run turbo -- run bundle --filter=@gitlab/duo-cli && bun run build:dev-binary && NODE_OPTIONS='--experimental-vm-modules' jest --config jest.e2e.config.js '--testMatch=<rootDir>/test/e2e/network/**/*.e2e.test.ts'
turboTURBO_TELEMETRY_DISABLED=1 turbo