PkgRadar

Package evidence

[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"console.log('ContextLine installed.\\n\\nNext step:\\n contextline setup\\n\\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\\n')\""

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.

Weekly downloads
145
Versions published
2
First published
May 2026
Publisher
vikas-x-dev

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

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":["[email protected]"],"fail_on":"high"}'

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":["[email protected]"],"fail_on":"high"}'
Publishervikas-x-dev
Artifact bytes40,422
Previous version0.1.0
Published2026-05-30T05:19:34.431Z
SHA-25625f0e0a906527f438ed904438f5d3a2bd6264ce4141d494b4b5bdf2f523c139e

Why flagged

What the scanner saw

Install Lifecycle Remote Or Exec: postinstall="node -e \"console.log('ContextLine installed.\\n\\nNext step:\\n contextline setup\\n\\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\\n')\""

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

Availability ledger

scan error

status
Last checked
noneRisk
Score
0.1.1Version

Latest scanner note: error decoding response body

Status history (2 events)
  1. availablescan_error · risk none · score · error decoding response body
  2. newavailable · risk high · score 35 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highInstall Lifecycle Remote Or Execpackage.jsonpostinstall="node -e \"console.log('ContextLine installed.\\n\\nNext step:\\n contextline setup\\n\\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\\n')\""30
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highInstall Lifecycle Remote Or Execpackage.jsonpostinstall="node -e \"console.log('ContextLine installed.\\n\\nNext step:\\n contextline setup\\n\\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\\n')\""30
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node -e \"console.log('ContextLine installed.\\n\\nNext step:\\n contextline setup\\n\\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\\n')\""5

Manifest

Package metadata

Scripts7
  • buildtsup
  • build:cleartsup && pwsh ../scripts/clear-codex.ps1
  • clearpwsh ../scripts/clear-codex.ps1
  • devtsx src/index.ts
  • linteslint .
  • postinstallnode -e "console.log('ContextLine installed.\n\nNext step:\n contextline setup\n\nThis will choose a memory folder, initialize .contextline, detect supported hosts, and configure MCP/hooks where possible.\n')"
  • testvitest run
Dependencies4
  • @modelcontextprotocol/sdk^1.12.1
  • commander^12.1.0
  • date-fns^3.6.0
  • zod^3.25.0