Package evidence

@github/[email protected]

Install-time lifecycle script: install="node package.js install"

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: 35
First published: Apr 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":["@github/[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":["@github/[email protected]"],"fail_on":"high"}'

PublisherGitHub Actions

Artifact bytes998,978

Previous version0.1.28

Published2026-06-02T03:16:25.058Z

SHA-25655be4aa0743718199049492b3c1dfb3a19ab134d9c9277f95a9cfac7c8a91a42

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: install added in 0.1.29 vs 0.1.28: "node package.js install"

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

Availability ledger

available

high

7d agoLast checked

highRisk

45Score

0.1.29Version

Status history (1 event)

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

Evidence

Static findings

1 static · 1 from release diff · showing high-signal first.

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	install added in 0.1.29 vs 0.1.28: "node package.js install"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	install added in 0.1.29 vs 0.1.28: "node package.js install"	40
low	Install-time lifecycle script	package.json	install="node package.js install"	5

Manifest

Package metadata

Scripts14

buildnode package.js build
build:jsesbuild src/index.ts src/main.ts --bundle --minify --legal-comments=none --format=esm --platform=node --packages=external --outdir=dist && dts-bundle-generator src/index.ts -o dist/index.d.ts --no-banner --export-referenced-types false
build:linuxcd computer/linux && bash build.sh
build:maccd computer/mac && bash build.sh
build:wincd computer/win && powershell -ExecutionPolicy Bypass -File build.ps1
cleannode package.js clean
installnode package.js install
linteslint package.js src/ test/
publish:majornpm version major -m "v%s" && git push && git push --tags
publish:minornpm version minor -m "v%s" && git push && git push --tags
publish:patchnpm version patch -m "v%s" && git push && git push --tags
servenpm run build:js && node dist/main.js
startnode package.js build start
testvitest run

Dependencies2

@modelcontextprotocol/sdk^1.27.1
zod^3.23.0