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 updateStatic 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"}'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
Status history (2 events)
- available → available · risk high · score 45 · status available -> available, risk high -> high, score 75 -> 45
- new → available · risk high · score 75 · status changed
Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.4 vs 1.3.3: "node bin/install-native.js" | 40 |
| medium | New Account With Lifecycle Hook | package.json | package first published 15 day(s) ago, 9 total version(s), has lifecycle hook | 10 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.4 vs 1.3.3: "node bin/install-native.js" | 40 |
| medium | New Account With Lifecycle Hook | package.json | package first published 15 day(s) ago, 9 total version(s), has lifecycle hook | 10 |
| low | Install-time lifecycle script | package.json | postinstall="node bin/install-native.js" | 5 |
Manifest
Package metadata
Scripts9
buildrm -rf dist/renderer && vite build && tsc -p tsconfig.json && pnpm run prepare:nativedevpnpm 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-builderpostinstallnode bin/install-native.jsprepare:nativenode bin/prepare-native.jsrebuildpnpm run rebuild:electronrebuild: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-sqlite3testpnpm run rebuild:node && vitest run
Dependencies2
better-sqlite3^12.0.0electron^33.0.0