Package evidence

@fiqihbadrian/[email protected]

New Account With Lifecycle Hook: package first published 3 day(s) ago, 6 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: 369
Versions published: 6
First published: Jun 2026
Publisher: fiqihbadrian

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.

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

Publisherfiqihbadrian

Artifact bytes215,413

Previous version1.0.6

Published2026-06-12T15:53:09.062Z

SHA-256252fab0afd5e00c4481af663b62c2f7bff9cbc7be4b62f3e2da9401f6a0000cc

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.0.7 vs 1.0.6: "cd backend && npm install --production"

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

Availability ledger

available

high

5h agoLast checked

highRisk

55Score

1.0.7Version

Status history (1 event)

new → available5h ago · risk high · score 55 · status changed

Evidence

Static findings

3 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.0.7 vs 1.0.6: "cd backend && npm install --production"	40
medium	New Account With Lifecycle Hook	package.json	package first published 3 day(s) ago, 6 total version(s), has lifecycle hook	10
medium	Suspicious Publish Context	manifest	{"package_age_days":3,"publisher":"fiqihbadrian","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}	10

Show all 4 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.0.7 vs 1.0.6: "cd backend && npm install --production"	40
medium	New Account With Lifecycle Hook	package.json	package first published 3 day(s) ago, 6 total version(s), has lifecycle hook	10
medium	Suspicious Publish Context	manifest	{"package_age_days":3,"publisher":"fiqihbadrian","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}	10
low	Install-time lifecycle script	package.json	postinstall="cd backend && npm install --production"	5

Manifest

Package metadata

Scripts9

buildnpm run build:frontend && npm run build:backend && npm run build:prepare
build:backendnode scripts/obfuscate-backend.js
build:frontendcd frontend && npm install && npm run build
build:preparemkdir -p backend/public && cp -r frontend/dist/* backend/public/
devconcurrently "npm run dev:backend" "npm run dev:frontend"
dev:backendcd backend && npm run dev
dev:frontendcd frontend && npm run dev
install:allnpm install && cd backend && npm install && cd ../frontend && npm install
postinstallcd backend && npm install --production

Dependencies4

chalk^4.1.2
get-port^5.1.1
inquirer^8.2.5
open^8.4.0