Package evidence

@breakedge/[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""

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: 3
First published: Jun 2026
Publisher: oss-breakedge-jp

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

Publisheross-breakedge-jp

Artifact bytes24,507

Previous version0.1.1

Published2026-06-06T05:47:51.823Z

SHA-256ade0a36c79693cba0c114f8e8f0112452a02cc0a8a9727b85a0cf733ab1bc07a

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.2 vs 0.1.1: "node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""

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

Availability ledger

available

high

8h agoLast checked

highRisk

75Score

0.1.2Version

Status history (1 event)

new → available8h ago · risk high · score 75 · status changed

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	postinstall added in 0.1.2 vs 0.1.1: "node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""	30

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.2 vs 0.1.1: "node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""	40
high	Install Lifecycle Remote Or Exec	package.json	postinstall="node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""	30
low	Install-time lifecycle script	package.json	postinstall="node -e \"try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}\""	5

Manifest

Package metadata

Scripts11

buildtsc && chmod +x dist/index.js
checkbiome check .
check:fixbiome check --fix .
devtsx src/index.ts
postinstallnode -e "try{require('fs').chmodSync('dist/index.js',0o755)}catch(e){}"
preparenpm run build
releasechangeset publish
startnode dist/index.js
testvitest run
test:covvitest run --coverage
typechecktsc --noEmit

Dependencies3

@modelcontextprotocol/sdk^1.12.0
yargs^17.0.0
zod^3.24.0