PkgRadar

Package evidence

@juliantanx/[email protected]

New Account With Lifecycle Hook: package first published 15 day(s) ago, 9 total version(s), has lifecycle hook

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
399
Versions published
9
First published
May 2026
Publisher
juliantanx

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":["@juliantanx/[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":["@juliantanx/[email protected]"],"fail_on":"high"}'
Publisherjuliantanx
Artifact bytes1,104,732
Previous version1.3.3
Published2026-05-29T02:27:04.333Z
SHA-256c270719c9cb5e7dec3e4d6e512876721746af6c6d721f3623d5b7bdba75f40ce

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.3.4 vs 1.3.3: "node bin/install-native.js"

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

Availability ledger

available

high
Last checked
highRisk
45Score
1.3.4Version
Status history (2 events)
  1. availableavailable · risk high · score 45 · status available -> available, risk high -> high, score 75 -> 45
  2. newavailable · risk high · score 75 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.3.4 vs 1.3.3: "node bin/install-native.js"40
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 15 day(s) ago, 9 total version(s), has lifecycle hook10
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.3.4 vs 1.3.3: "node bin/install-native.js"40
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 15 day(s) ago, 9 total version(s), has lifecycle hook10
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node bin/install-native.js"5

Manifest

Package metadata

Scripts9
  • buildrm -rf dist/renderer && vite build && tsc -p tsconfig.json && pnpm run prepare:native
  • devpnpm run prepare:native && concurrently --names "vite,tsc,electron" --kill-others --success command-electron "vite build --watch" "tsc -p tsconfig.json --watch" "node -e \"require('wait-on')({resources:['dist/main.js']},()=>{const c=require('child_process').spawn(require('electron'),['.'],{stdio:'inherit'});c.on('exit',(code,signal)=>process.exit(code ?? (signal ? 1 : 0)))})\""
  • packpnpm build && electron-builder
  • postinstallnode bin/install-native.js
  • prepare:nativenode bin/prepare-native.js
  • rebuildpnpm run rebuild:electron
  • rebuild:electronnode -e "const {rebuild}=require('@electron/rebuild');const v=require('electron/package.json').version;rebuild({buildPath:process.cwd(),electronVersion:v,onlyModules:['better-sqlite3'],force:true}).then(()=>process.exit(0)).catch(e=>{console.error(e);process.exit(1)})"
  • rebuild:nodenpm rebuild better-sqlite3
  • testpnpm run rebuild:node && vitest run
Dependencies2
  • better-sqlite3^12.0.0
  • electron^33.0.0