Package evidence

@zagents/[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"cvsz","burst_same_day":3,"burst_week":3,"lure":null,"version_anomaly":false,"new_account":false}

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: 2
First published: Jun 2026
Publisher: cvsz

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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

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

Publishercvsz

Artifact bytes20,128

Previous version0.1.2

Published2026-06-20T06:03:03.358Z

SHA-2563ff9d2d9858056c03e64bd0c1d2734475e5778063cb9339d797ed802f8d423ac

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"cvsz","burst_same_day":3,"burst_week":3,"lure":null,"version_anomaly":false,"new_account":false}

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

Availability ledger

available

review

11h agoLast checked

reviewRisk

10Score

0.1.3Version

Status history (1 event)

new → available11h ago · risk review · score 10 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
medium	Suspicious Publish Context	manifest	{"package_age_days":0,"publisher":"cvsz","burst_same_day":3,"burst_week":3,"lure":null,"version_anomaly":false,"new_account":false}	10

Manifest

Package metadata

Scripts4

buildtsc
build:wasmRUSTFLAGS= wasm-pack build ../../crates/kernel-wasm --target nodejs --release --out-dir ../../packages/kernel-js/pkg && rm -f pkg/.gitignore && node -e "const f=require('fs');const j=require('./pkg/package.json');j.type='commonjs';f.writeFileSync('./pkg/package.json',JSON.stringify(j,null,2)+'\n')"
linttsc --noEmit
testvitest run

Dependencies1

@ruvector/emergent-time^0.1.0

Optional dependencies5

@zagents/kernel-darwin-arm64^0.1.0
@zagents/kernel-darwin-x64^0.1.0
@zagents/kernel-linux-arm64-gnu^0.1.0
@zagents/kernel-linux-x64-gnu^0.1.0
@zagents/kernel-win32-x64-msvc^0.1.0