Package evidence

@persona/[email protected]

Install Lifecycle Suppresses Failure: postinstall="test -d .git && git config core.hooksPath .githooks || true"

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.

Versions published: 5
First published: May 2026
Publisher: GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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

PublisherGitHub Actions

Artifact bytes198,414

Previous version0.1.2

Published2026-05-15T22:06:35.421Z

SHA-256603145192997f29e7943954ea4706c44a75951c829ce7a0d5a6614fe1c323ee7

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.3 vs 0.1.2: "test -d .git && git config core.hooksPath .githooks || true"

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

Availability ledger

available

high

41h agoLast checked

highRisk

65Score

0.1.3Version

Status history (1 event)

new → available41h ago · risk high · score 65 · 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 0.1.3 vs 0.1.2: "test -d .git && git config core.hooksPath .githooks \|\| true"	40
high	Install Lifecycle Suppresses Failure	package.json	postinstall="test -d .git && git config core.hooksPath .githooks \|\| true"	20
medium	New Account With Lifecycle Hook	package.json	package first published 32 day(s) ago, 5 total version(s), has lifecycle hook	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 0.1.3 vs 0.1.2: "test -d .git && git config core.hooksPath .githooks \|\| true"	40
high	Install Lifecycle Suppresses Failure	package.json	postinstall="test -d .git && git config core.hooksPath .githooks \|\| true"	20
medium	New Account With Lifecycle Hook	package.json	package first published 32 day(s) ago, 5 total version(s), has lifecycle hook	10
low	Install-time lifecycle script	package.json	postinstall="test -d .git && git config core.hooksPath .githooks \|\| true"	5

Manifest

Package metadata

Scripts12

buildvite build --config vite.lib.config.ts
devvite build --config vite.lib.config.ts --watch & vite --config vite.config.ts
formatoxfmt
format:checkoxfmt --check
lintoxlint
lint:fixoxlint --fix
postinstalltest -d .git && git config core.hooksPath .githooks || true
testvitest run
test:browservitest --project browser
test:browser:headedvitest --project browser --browser.headless=false
test:unitvitest --project unit
typechecktsc --noEmit

Dependencies1

qs^6.13.0