Package evidence

[email protected]

Native Binary Main Entry: main/bin entry points to a compiled binary: bin entry

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: 17
First published: Jun 2026
Publisher: kakaman_

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

Publisherkakaman_

Artifact bytes3,029

Previous version0.1.1

Published2026-06-11T16:27:34.699Z

SHA-256388eccb774bfb23a79a522925556bc3bd8b19eb24abe60d438be6d0fba8edf4e

Why flagged

What the scanner saw

Native Binary Main Entry: main/bin entry points to a compiled binary: bin entry

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

Availability ledger

available

high

5h agoLast checked

highRisk

100Score

1.0.0Version

Status history (1 event)

new → available5h ago · risk high · score 100 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	Native Binary Main Entry	package.json	main/bin entry points to a compiled binary: bin entry	45
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.0.0 vs 0.1.1: "node ./postinstall.mjs"	40
medium	Suspicious Publish Context	manifest	{"package_age_days":2,"publisher":"kakaman_","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false}	10

Show all 4 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	Native Binary Main Entry	package.json	main/bin entry points to a compiled binary: bin entry	45
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.0.0 vs 0.1.1: "node ./postinstall.mjs"	40
medium	Suspicious Publish Context	manifest	{"package_age_days":2,"publisher":"kakaman_","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false}	10
low	Install-time lifecycle script	package.json	postinstall="node ./postinstall.mjs"	5

Manifest

Package metadata

Scripts1

postinstallnode ./postinstall.mjs

Optional dependencies1

maia-code-windows-x641.0.0