PkgRadar

Package evidence

@inline-one/[email protected]

Install Lifecycle Remote Or Exec: prepare="node scripts/build.js"

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":["@inline-one/[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":["@inline-one/[email protected]"],"fail_on":"high"}'
Publisherinlineone
Artifact bytes42,388
Previous version0.1.0
Published2026-05-24T16:04:42.256Z
SHA-256ea9f1c719ef3d35a9f590c11bc23cc8a79ae1ea6569b9980abcaae92ac831e63

Why flagged

What the scanner saw

Install Lifecycle Remote Or Exec: prepare="node scripts/build.js"

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

Availability ledger

not present

status
Last checked
noneRisk
Score
0.1.1Version

Latest scanner note: @inline-one/[email protected] not present in registry metadata

Status history (2 events)
  1. availablenot_present · risk none · score · @inline-one/[email protected] not present in registry metadata
  2. newavailable · risk high · score 34 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

inlineone

5 members · evidence strength 70
Repeated static TTPstale

Install Lifecycle Remote Or Exec — prepare="node scripts/build.js"

5 members · evidence strength 76

Evidence

Static findings

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

SeverityKindPathDetailPoints
highInstall Lifecycle Remote Or Execpackage.jsonprepare="node scripts/build.js"30
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highInstall Lifecycle Remote Or Execpackage.jsonprepare="node scripts/build.js"30
lowInstall-time lifecycle scriptpackage.jsonprepare="node scripts/build.js"4

Manifest

Package metadata

Scripts4
  • buildnode scripts/build.js
  • devnode scripts/build.js --watch
  • preparenode scripts/build.js
  • testvitest run