PkgRadar

Package evidence

[email protected]

New Account With Lifecycle Hook: package first published 0 day(s) ago, 1 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.

Versions published
1
First published
Jun 2026
Publisher
sevenecks

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.

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"}'
Publishersevenecks
Artifact bytes246,101
Previous versionnone
Published2026-06-09T02:21:28.578Z
SHA-25616ea4e9d3b6b60c771f8e638ea9862b7898e6aaa72058612966d25e666f3e6be

Why flagged

What the scanner saw

New Account With Lifecycle Hook: package first published 0 day(s) ago, 1 total version(s), has lifecycle hook

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

Availability ledger

available

high
Last checked
highRisk
5Score
0.2.5Version
Status history (1 event)
  1. newavailable · risk high · score 5 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Account With Lifecycle Hookpackage.jsonpackage first published 0 day(s) ago, 1 total version(s), has lifecycle hook25
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Account With Lifecycle Hookpackage.jsonpackage first published 0 day(s) ago, 1 total version(s), has lifecycle hook25
lowInstall-time lifecycle scriptpackage.jsoninstall="node-gyp-build"5

Manifest

Package metadata

Scripts14
  • build:wasmnode -e "require('fs').mkdirSync('dist', { recursive: true })" && tree-sitter build --wasm -o dist/tree-sitter-moo.wasm
  • cinpm run generate && npm test && npm run validate:fixtures && npm run build:wasm && npm run validate:wasm
  • generatetree-sitter generate
  • import:fixturesnode scripts/import-fixtures.js
  • import:fixtures:allnode scripts/import-fixtures.js --all
  • installnode-gyp-build
  • parse:fixturesnpm run validate:fixtures
  • prebuildifyprebuildify --napi --strip
  • prepare:packagenpm run generate && npm run build:wasm
  • smoke:nativenode scripts/smoke-native.js
  • smoke:packagenode scripts/smoke-package.js
  • testenv HOME=/tmp TREE_SITTER_DIR=/tmp tree-sitter test --config-path tree-sitter-config.json
  • validate:fixturesenv HOME=/tmp TREE_SITTER_DIR=/tmp node scripts/validate-fixtures.js fixtures/valid
  • validate:wasmnode -e "const fs = require('fs'); const wasm = fs.readFileSync('dist/tree-sitter-moo.wasm'); if (!WebAssembly.validate(wasm)) throw new Error('dist/tree-sitter-moo.wasm failed WebAssembly.validate');"
Dependencies2
  • node-addon-api^8.8.0
  • node-gyp-build^4.8.0