PkgRadar

Package evidence

@linuxctrl/[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"linuxctrl","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":true}

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
2
First published
Jun 2026
Publisher
linuxctrl

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["@linuxctrl/[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":["@linuxctrl/[email protected]"],"fail_on":"review"}'
Publisherlinuxctrl
Artifact bytes327,858
Previous versionnone
Published2026-06-20T15:57:48.034Z
SHA-256b8f78c7c5ed8cd56b81f39a99e79eacf6a69f9fdcac65122e0c8213ced547639

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"linuxctrl","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":true}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
0.1.1Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"linuxctrl","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":true}10

Manifest

Package metadata

Scripts9
  • buildbun run build:lib && bun run build:cli && bun run build:types
  • build:cliNODE_ENV=production bun build src/cli/index.tsx --outfile dist/cli.js --target node --format esm --define 'process.env.NODE_ENV="production"' && sed -i 's|#!/usr/bin/env bun|#!/usr/bin/env node|' dist/cli.js && sed -i '2{/^\/\/ @bun/d}' dist/cli.js
  • build:libbun build src/index.ts --outfile dist/index.js --target node --format esm && bun build src/index.ts --outfile dist/index.cjs --target node --format cjs
  • build:typestsc -p tsconfig.build.json --emitDeclarationOnly --declaration --outDir dist
  • clibun run src/cli/index.tsx
  • devbun run src/cli/index.tsx --dev
  • prepublishOnlybun run build
  • startbun run src/cli/index.tsx
  • typechecktsc --noEmit
Dependencies3
  • ink^7.0.6
  • react^19.2.7
  • react-devtools-core^7.0.1