Package evidence

@baykar/[email protected]

New Account With Lifecycle Hook: package first published 23 day(s) ago, 3 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: 7
Versions published: 3
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":["@baykar/[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":["@baykar/[email protected]"],"fail_on":"high"}'

PublisherGitHub Actions

Artifact bytes1,718

Previous version0.0.0-development

Published2026-05-18T17:09:55.583Z

SHA-256f05851a5fa22e7217e2e8b43195bb6441261123b91bac4603737157caec19df4

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: preinstall added in 0.0.0 vs 0.0.0-development: "npx only-allow pnpm"

1 candidate cluster(s) currently reference this release.

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

Availability ledger

available

high

7h agoLast checked

highRisk

45Score

0.0.0Version

Status history (1 event)

new → available7h ago · risk high · score 45 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burstactive

GitHub Actions

157 members · evidence strength 84

Publisher / release actor burstcandidate

GitHub Actions

157 members · max score 283

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	preinstall added in 0.0.0 vs 0.0.0-development: "npx only-allow pnpm"	40
high	New Account With Lifecycle Hook	package.json	package first published 23 day(s) ago, 3 total version(s), has lifecycle hook	25

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	preinstall added in 0.0.0 vs 0.0.0-development: "npx only-allow pnpm"	40
high	New Account With Lifecycle Hook	package.json	package first published 23 day(s) ago, 3 total version(s), has lifecycle hook	25
low	Install-time lifecycle script	package.json	preinstall="npx only-allow pnpm"	5

Manifest

Package metadata

Scripts3

buildsvelte-package -i ./src -o ./dist
ci:publishpnpm publish -r --no-git-checks
preinstallnpx only-allow pnpm