Package evidence

@tapsmith/[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}\""

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: 4
Versions published: 2
First published: Apr 2026
Publisher: samsmithyeah

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

Publishersamsmithyeah

Artifact bytes4,208,350

Previous versionnone

Published2026-04-24T16:14:11.523Z

SHA-25683b062934c0a6f34dfbaffbe3a2a503b68e5792a1839e73ffd478d75d5e20a31

Why flagged

What the scanner saw

Install Lifecycle Remote Or Exec: postinstall="node -e \"try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}\""

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

Availability ledger

available

high

13h agoLast checked

highRisk

35Score

0.1.1Version

Status history (1 event)

new → available13h ago · risk high · score 35 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}\""	30
medium	New Account With Lifecycle Hook	package.json	package first published 45 day(s) ago, 2 total version(s), has lifecycle hook	10

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}\""	30
medium	New Account With Lifecycle Hook	package.json	package first published 45 day(s) ago, 2 total version(s), has lifecycle hook	10
low	Install-time lifecycle script	package.json	postinstall="node -e \"try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}\""	5

Manifest

Package metadata

Scripts1

postinstallnode -e "try{require('fs').chmodSync('tapsmith-core',0o755)}catch(e){console.warn('tapsmith: chmod failed:',e.message)}"